CVE-2026-2811Ajaxify Comments < 3.2 - Unauthenticated HTTP Header Injection
Updated under an hour ago ()
Does this affect you?
It affects Unknown Ajaxify Comments. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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
- 5.4 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
- Weakness (CWE)
- CWE-113
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- WPScan
- NVD analysis
- Deferred
- Record last updated
- Sep 2, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Unknown Ajaxify Comments unknown:ajaxify_comments (from the name) | before 3.2 | CNA record |
References
- https://wpscan.com/vulnerability/48250628-9b81-4bef-b623-356ceca01215/exploit, vdb-entry, technical-description
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.