CVE-2026-2811 json
Ajaxify Comments < 3.2 - Unauthenticated HTTP Header Injection
published 2mo ago modified 2mo ago also EUVD-2026-70050
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 20%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Unknown Ajaxify Comments 3.2
Is CVE-2026-2811 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/48250628-9b81-4bef-b623-356ceca01215/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N |
Affected products
- Unknown Ajaxify Comments
Classification
- Weakness
-
- CWE-113 Improper Neutralization of CRLF Sequences in HTTP Headers
- Technology feeds
References
-
wpscan.com
/vulnerability/48250628-9b81-4bef-b623-356ceca01215/
exploit, vdb-entry, technical-description
Sources
- CVE List CVE-2026-2811
- NVD CVE-2026-2811
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.