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

Vendors Products
Wordpress-extensions Subscribe
Ajaxify Comments Subscribe
Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Wed, 11 Nov 2026 21:45:00 +0000

Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions ajaxify Comments
Vendors & Products Wordpress-extensions
Wordpress-extensions ajaxify Comments

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

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-09-02T14:57:35.380Z

Reserved: 2026-02-19T15:54:12.930Z

Link: CVE-2026-2811

cve-icon Vulnrichment

Updated: 2026-09-02T14:42:50.790Z

cve-icon NVD

Status : Deferred

Published: 2026-09-02T15:17:38.270

Modified: 2026-09-03T17:50:37.690

Link: CVE-2026-2811

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-11T21:16:17Z

Weaknesses