CVE-2026-9731

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-07-08. 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 Wp Js Detect plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.9. This is due to missing or incorrect nonce validation on the plugin_settings function. This makes it possible for unauthenticated attackers to update the plugin's notification text and CSS settings (wp_non_js_notification_text and wp_non_js_notification_css), injecting arbitrary content that is echoed unescaped on the frontend via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
19(Track)
EG Risk 19/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 8, 2026

References (5)

Vendor Advisories for CVE-2026-9731(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 19× in last 7d / 48× 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-02 02:27 UTCEPSS rescore
  2. 2026-08-02 00:52 UTCEG score recompute
  3. 2026-08-02 00:52 UTCGHSA enrichment
  4. 2026-08-01 04:16 UTCEPSS rescore
  5. 2026-07-31 23:24 UTCGHSA enrichment
  6. 2026-07-30 21:54 UTCEG score recompute
  7. 2026-07-30 21:54 UTCGHSA enrichment
  8. 2026-07-30 16:28 UTCEPSS rescore
  9. 2026-07-30 01:30 UTCEPSS rescore
  10. 2026-07-29 19:05 UTCGHSA enrichment
  11. 2026-07-28 17:16 UTCEG score recompute
  12. 2026-07-28 17:16 UTCGHSA enrichment
  13. 2026-07-28 15:37 UTCEPSS rescore
  14. 2026-07-27 15:42 UTCEG score recompute
  15. 2026-07-27 15:42 UTCGHSA enrichment
  16. 2026-07-27 14:14 UTCEPSS rescore
  17. 2026-07-26 14:54 UTCEPSS rescore
  18. 2026-07-26 12:31 UTCEG score recompute
  19. 2026-07-26 12:31 UTCGHSA enrichment
  20. 2026-07-25 14:18 UTCEPSS rescore
  21. 2026-07-24 14:18 UTCEPSS rescore
  22. 2026-07-23 14:18 UTCEPSS rescore
  23. 2026-07-23 03:23 UTCEG score recompute
  24. 2026-07-22 14:08 UTCEPSS rescore
  25. 2026-07-21 15:25 UTCEPSS rescore
Show 23 more
  1. 2026-07-20 17:08 UTCEPSS rescore
  2. 2026-07-19 14:31 UTCEPSS rescore
  3. 2026-07-19 02:29 UTCEPSS rescore
  4. 2026-07-18 10:04 UTCEPSS rescore
  5. 2026-07-16 17:21 UTCGHSA enrichment
  6. 2026-07-16 17:03 UTCEPSS rescore
  7. 2026-07-15 16:57 UTCEPSS rescore
  8. 2026-07-15 15:54 UTCGHSA enrichment
  9. 2026-07-15 02:00 UTCEPSS rescore
  10. 2026-07-14 14:28 UTCGHSA enrichment
  11. 2026-07-13 22:31 UTCEPSS rescore
  12. 2026-07-13 13:00 UTCGHSA enrichment
  13. 2026-07-13 06:13 UTCEPSS rescore
  14. 2026-07-12 11:32 UTCGHSA enrichment
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-11 10:05 UTCGHSA enrichment
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-10 08:37 UTCGHSA enrichment
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 07:09 UTCGHSA enrichment
  21. 2026-07-08 15:16 UTCEPSS rescore
  22. 2026-07-08 05:42 UTCEG score recompute
  23. 2026-07-08 05:40 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9731?
CVE-2026-9731 is a medium vulnerability published on July 8, 2026. The Wp Js Detect plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.9. This is due to missing or incorrect nonce validation on the pluginsettings function. This makes it possible for unauthenticated attackers to update the plugin's…
When was CVE-2026-9731 disclosed?
CVE-2026-9731 was first published in the National Vulnerability Database on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9731 actively exploited?
CVE-2026-9731 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 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-9731?
CVE-2026-9731 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-9731?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9731, 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-9731

Explore →

Is Your Infrastructure Affected by CVE-2026-9731?

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

Start Free Scan →Browse All CVEs