CVE-2026-6405

MEDIUMNVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

Score 4.3 from GitHub Security Advisory published 2026-05-20. NVD baseline CVSS 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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 Anomify AI – Anomaly Detection and Alerting plugin for WordPress is vulnerable to Cross-Site Request Forgery (CSRF) leading to Stored Cross-Site Scripting (XSS) in versions up to and including 0.3.6. This is due to missing nonce verification on the settings page handler and insufficient output escaping in the admin_options.php template. The settings form includes no wp_nonce_field() and the handler performs no check_admin_referer() check, meaning any cross-origin POST can modify plugin settings. The API key field is sanitized only with sanitize_text_field(), which strips HTML tags but does not encode double-quote characters; the value is then rendered into an HTML attribute via bare echo without esc_attr(), allowing a double-quote attribute-escape payload to survive both sanitization and storage. This makes it possible for unauthenticated attackers to inject arbitrary web scripts by tricking a logged-in administrator into visiting a malicious page that submits a forged request, storing the payload in the database and causing it to execute in the administrator's browser whenever the plugin settings page is visited.

CVSS v3
4.3
EG Score
4.3(medium)
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
6%
KEV
Not listed

Published

May 20, 2026

Last Modified

July 24, 2026

References (7)

Vendor Advisories for CVE-2026-6405(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 12× in last 7d / 50× 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.

Showing the most recent 100 of 126 total refreshes for this CVE.

  1. 2026-08-02 02:27 UTCEPSS rescore
  2. 2026-08-01 17:45 UTCEG score recompute
  3. 2026-08-01 17:45 UTCGHSA enrichment
  4. 2026-08-01 04:16 UTCEPSS rescore
  5. 2026-07-30 16:28 UTCEPSS rescore
  6. 2026-07-30 01:30 UTCEPSS rescore
  7. 2026-07-28 15:37 UTCEPSS rescore
  8. 2026-07-27 14:14 UTCEPSS rescore
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-26 14:54 UTCEPSS rescore
  11. 2026-07-26 08:16 UTCEG score recompute
  12. 2026-07-26 08:15 UTCGHSA enrichment
  13. 2026-07-25 14:18 UTCEPSS rescore
  14. 2026-07-25 14:18 UTCEPSS rescore
  15. 2026-07-24 14:18 UTCEPSS rescore
  16. 2026-07-24 14:18 UTCEPSS rescore
  17. 2026-07-23 14:18 UTCEPSS rescore
  18. 2026-07-23 14:18 UTCEPSS rescore
  19. 2026-07-23 03:22 UTCEG score recompute
  20. 2026-07-22 14:08 UTCEPSS rescore
  21. 2026-07-22 14:08 UTCEPSS rescore
  22. 2026-07-21 15:25 UTCEPSS rescore
  23. 2026-07-21 15:25 UTCEPSS rescore
  24. 2026-07-20 17:08 UTCEPSS rescore
  25. 2026-07-19 14:31 UTCEPSS rescore
Show 75 more
  1. 2026-07-18 10:04 UTCEPSS rescore
  2. 2026-07-16 17:03 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-13 22:31 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-08 15:16 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-06 02:23 UTCEPSS rescore
  22. 2026-07-05 02:31 UTCEPSS rescore
  23. 2026-07-05 02:30 UTCEPSS rescore
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-04 06:31 UTCEPSS rescore
  26. 2026-07-01 15:07 UTCEPSS rescore
  27. 2026-06-30 23:22 UTCEPSS rescore
  28. 2026-06-29 20:30 UTCGHSA enrichment
  29. 2026-06-29 14:06 UTCEPSS rescore
  30. 2026-06-28 14:07 UTCEPSS rescore
  31. 2026-06-28 04:56 UTCEPSS rescore
  32. 2026-06-27 20:17 UTCGHSA enrichment
  33. 2026-06-27 03:08 UTCEPSS rescore
  34. 2026-06-26 19:35 UTCGHSA enrichment
  35. 2026-06-25 16:16 UTCGHSA enrichment
  36. 2026-06-25 13:50 UTCEPSS rescore
  37. 2026-06-24 14:05 UTCEPSS rescore
  38. 2026-06-23 21:33 UTCEPSS rescore
  39. 2026-06-23 21:33 UTCEPSS rescore
  40. 2026-06-22 14:25 UTCEPSS rescore
  41. 2026-06-22 14:25 UTCEPSS rescore
  42. 2026-06-21 14:56 UTCEPSS rescore
  43. 2026-06-21 14:56 UTCEPSS rescore
  44. 2026-06-21 01:59 UTCEPSS rescore
  45. 2026-06-21 01:59 UTCEPSS rescore
  46. 2026-06-19 19:26 UTCEPSS rescore
  47. 2026-06-19 19:26 UTCEPSS rescore
  48. 2026-06-18 17:52 UTCEPSS rescore
  49. 2026-06-18 17:52 UTCEPSS rescore
  50. 2026-06-17 20:40 UTCGHSA enrichment
  51. 2026-06-17 17:53 UTCEPSS rescore
  52. 2026-06-16 20:15 UTCGHSA enrichment
  53. 2026-06-16 17:53 UTCEPSS rescore
  54. 2026-06-15 17:49 UTCEPSS rescore
  55. 2026-06-15 17:49 UTCEPSS rescore
  56. 2026-06-15 15:52 UTCGHSA enrichment
  57. 2026-06-14 23:18 UTCEPSS rescore
  58. 2026-06-14 08:09 UTCGHSA enrichment
  59. 2026-06-13 23:00 UTCEPSS rescore
  60. 2026-06-13 07:45 UTCGHSA enrichment
  61. 2026-06-12 23:12 UTCEPSS rescore
  62. 2026-06-12 23:12 UTCEPSS rescore
  63. 2026-06-12 07:16 UTCGHSA enrichment
  64. 2026-06-11 14:00 UTCEPSS rescore
  65. 2026-06-11 06:53 UTCGHSA enrichment
  66. 2026-06-10 22:19 UTCEPSS rescore
  67. 2026-06-10 06:30 UTCGHSA enrichment
  68. 2026-06-09 06:07 UTCGHSA enrichment
  69. 2026-06-08 14:17 UTCEPSS rescore
  70. 2026-06-08 05:38 UTCGHSA enrichment
  71. 2026-06-07 15:25 UTCEPSS rescore
  72. 2026-06-07 05:15 UTCGHSA enrichment
  73. 2026-06-06 13:47 UTCEPSS rescore
  74. 2026-06-06 04:52 UTCGHSA enrichment
  75. 2026-06-05 22:47 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-6405?
CVE-2026-6405 is a medium vulnerability published on May 20, 2026. The Anomify AI – Anomaly Detection and Alerting plugin for WordPress is vulnerable to Cross-Site Request Forgery (CSRF) leading to Stored Cross-Site Scripting (XSS) in versions up to and including 0.3.6. This is due to missing nonce verification on the settings page handler and insufficient output…
When was CVE-2026-6405 disclosed?
CVE-2026-6405 was first published in the National Vulnerability Database on May 20, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6405 actively exploited?
CVE-2026-6405 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 93.5% of all scored CVEs.
What is the CVSS score of CVE-2026-6405?
CVE-2026-6405 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-6405?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6405, 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-6405

Explore →

Is Your Infrastructure Affected by CVE-2026-6405?

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

Start Free Scan →Browse All CVEs