CVE-2026-9616

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

Score 4.3 from GitHub Security Advisory published 2026-06-24. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The Generate Security.txt plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.0.12. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete the site's security.txt file from the server filesystem or create the .well-known directory by directly invoking the delete_securitytxt or create_wellknown_folder AJAX actions.

CVSS v3
4.3
EG Score
4.3(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 25, 2026

References (7)

Vendor Advisories for CVE-2026-9616(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 59× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-03 14:14 UTCEG score recompute
  2. 2026-08-03 14:14 UTCGHSA enrichment
  3. 2026-08-03 10:36 UTCEPSS rescore
  4. 2026-08-02 09:26 UTCEG score recompute
  5. 2026-08-02 09:26 UTCGHSA enrichment
  6. 2026-08-02 02:27 UTCEPSS rescore
  7. 2026-08-01 07:44 UTCEG score recompute
  8. 2026-08-01 07:44 UTCGHSA enrichment
  9. 2026-08-01 04:16 UTCEPSS rescore
  10. 2026-07-31 04:32 UTCEG score recompute
  11. 2026-07-31 04:32 UTCGHSA enrichment
  12. 2026-07-30 02:50 UTCEG score recompute
  13. 2026-07-30 02:50 UTCGHSA enrichment
  14. 2026-07-30 01:30 UTCEPSS rescore
  15. 2026-07-29 01:07 UTCEG score recompute
  16. 2026-07-29 01:07 UTCGHSA enrichment
  17. 2026-07-28 15:37 UTCEPSS rescore
  18. 2026-07-27 17:44 UTCEG score recompute
  19. 2026-07-27 17:44 UTCGHSA enrichment
  20. 2026-07-27 14:14 UTCEPSS rescore
  21. 2026-07-26 15:46 UTCEG score recompute
  22. 2026-07-26 15:46 UTCGHSA enrichment
  23. 2026-07-26 14:54 UTCEPSS rescore
  24. 2026-07-25 14:18 UTCEPSS rescore
  25. 2026-07-24 14:18 UTCEPSS rescore
Show 54 more
  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:23 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 20:16 UTCGHSA enrichment
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-15 18:11 UTCGHSA enrichment
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-14 16:29 UTCGHSA enrichment
  16. 2026-07-13 22:31 UTCEPSS rescore
  17. 2026-07-13 14:47 UTCGHSA enrichment
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-12 13:05 UTCGHSA enrichment
  20. 2026-07-12 05:46 UTCEPSS rescore
  21. 2026-07-11 11:20 UTCGHSA enrichment
  22. 2026-07-11 08:27 UTCEPSS rescore
  23. 2026-07-10 09:37 UTCGHSA enrichment
  24. 2026-07-09 19:10 UTCEPSS rescore
  25. 2026-07-09 07:39 UTCGHSA enrichment
  26. 2026-07-08 15:16 UTCEPSS rescore
  27. 2026-07-08 05:57 UTCGHSA enrichment
  28. 2026-07-07 13:46 UTCEPSS rescore
  29. 2026-07-07 04:12 UTCGHSA enrichment
  30. 2026-07-06 16:27 UTCEPSS rescore
  31. 2026-07-06 02:26 UTCGHSA enrichment
  32. 2026-07-06 02:23 UTCEPSS rescore
  33. 2026-07-05 02:31 UTCEPSS rescore
  34. 2026-07-05 00:41 UTCGHSA enrichment
  35. 2026-07-04 06:31 UTCEPSS rescore
  36. 2026-07-03 22:59 UTCGHSA enrichment
  37. 2026-07-02 21:15 UTCGHSA enrichment
  38. 2026-07-01 19:32 UTCGHSA enrichment
  39. 2026-07-01 15:07 UTCEPSS rescore
  40. 2026-06-30 23:22 UTCEPSS rescore
  41. 2026-06-30 17:50 UTCGHSA enrichment
  42. 2026-06-29 16:08 UTCGHSA enrichment
  43. 2026-06-29 14:06 UTCEPSS rescore
  44. 2026-06-28 14:26 UTCGHSA enrichment
  45. 2026-06-28 14:07 UTCEPSS rescore
  46. 2026-06-28 04:56 UTCEPSS rescore
  47. 2026-06-27 12:44 UTCGHSA enrichment
  48. 2026-06-27 03:08 UTCEPSS rescore
  49. 2026-06-26 11:01 UTCGHSA enrichment
  50. 2026-06-25 13:50 UTCEPSS rescore
  51. 2026-06-25 09:14 UTCGHSA enrichment
  52. 2026-06-24 14:05 UTCEPSS rescore
  53. 2026-06-24 07:32 UTCEG score recompute
  54. 2026-06-24 07:29 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9616?
CVE-2026-9616 is a medium vulnerability published on June 24, 2026. The Generate Security.txt plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.0.12. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with…
When was CVE-2026-9616 disclosed?
CVE-2026-9616 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9616 actively exploited?
CVE-2026-9616 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.7% of all scored CVEs.
What is the CVSS score of CVE-2026-9616?
CVE-2026-9616 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-9616?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9616, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-9616

Explore →

Is Your Infrastructure Affected by CVE-2026-9616?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs