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.
Project Subscriptions
No data.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Wed, 02 Sep 2026 10:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Ajaxify Comments < 3.2 - Unauthenticated HTTP Header Injection | |
| Weaknesses | CWE-113 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: WPScan
Published:
Updated: 2026-09-02T14:57:35.380Z
Reserved: 2026-02-19T15:54:12.930Z
Link: CVE-2026-2811
Updated: 2026-09-02T14:42:50.790Z
Status : Received
Published: 2026-09-02T15:17:38.270
Modified: 2026-09-02T15:17:38.270
Link: CVE-2026-2811
No data.
OpenCVE Enrichment
No data.
Weaknesses