CVE-2026-2811
mediumThe Ajaxify Comments WordPress plugin before 3.2 is vulnerable to HTTP Header Injection due to insufficient input sanitization and output escaping on user-supp…
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
5.4 (CVSS v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N Severity source: NVD CVSS v3.1 (contact@wpscan.com)
Timeline (UTC)
Published: 2026-09-02 15:17
Modified: 2026-09-03 17:50
NVD status: Deferred
Last synced 1 day ago
Verified against the source API 2026-10-27 06:50 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).
Affected products
Not reported by the source (unknown — not "none").
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://wpscan.com/vulnerability/48250628-9b81-4bef-b623-356ceca01215/ contact@wpscan.com
Data sources
NVD CVE API 2.0 — fetched 2026-10-27 06:50 UTC · record ↗