Ajaxify Comments < 3.2 - Unauthenticated HTTP Header Injection
Priority LOW 24CWE-113Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
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.
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00275 20th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by the CNA
Fix Fixed Ajaxify Comments (Unknown): 3.2
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | Ajaxify Comments | before 3.2 | 3.2 | Patch available | CNA |
- Ajaxify Comments VendorUnknown Affected before 3.2 Fixed in 3.2 Patch available CNA
Remediation
- Fix · CNA Ajaxify Comments (Unknown) Fixed in 3.2
Timeline
- 2026-10-02 Threatist record created from CVE-2026-2811
- 2026-10-03 Alias added: GHSA-jxm3-h8qw-wgcx
References
Sources
- CVE-2026-2811 · CVE Program
- CVE-2026-2811 · NVD
- FIRST EPSS
- GHSA-jxm3-h8qw-wgcx · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences