CVE-2026-2811

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-09-02. a secondary CVSS source baseline 5.4; sources differ by 0.0.

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

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

The Ajaxify Comments WordPress plugin before 3.2 is vulnerable to HTTP Header Injection due to insufficient input sanitization and output escaping on user-supplied data. This makes it possible for unauthenticated attackers to inject arbitrary HTTP headers.

CVSS v3
5.4
EG Score
5.4(high)
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
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

September 2, 2026

Last Modified

September 3, 2026

Advisory Details (1)

Auto-updated Sep 2, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Ajaxify Comments < 3.2 – Unauthenticated HTTP Header Injection | CVE 2026-2811 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/48250628-9b81-4bef-b623-356ceca01215/

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

Frequently asked(5)

What is CVE-2026-2811?
CVE-2026-2811 is a medium vulnerability published on September 2, 2026. The Ajaxify Comments WordPress plugin before 3.2 is vulnerable to HTTP Header Injection due to insufficient input sanitization and output escaping on user-supplied data. This makes it possible for unauthenticated attackers to inject arbitrary HTTP headers.
When was CVE-2026-2811 disclosed?
CVE-2026-2811 was first published in the National Vulnerability Database on September 2, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-2811 actively exploited?
CVE-2026-2811 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-2811?
CVE-2026-2811 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-2811?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2811, 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-2811

Explore →

Is Your Infrastructure Affected by CVE-2026-2811?

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

Start Free Scan →Browse All CVEs