CVE-2026-2811 | BDVDB-2026-367239 Detail

Ajaxify Comments

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.

Impact#

Per CVSS v3.1: confidentiality impact low, integrity impact low, availability impact none. Attack vector: network.

Weaknesses#

CWE-113 Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')

References#

https://wpscan.com/vulnerability/48250628-9b81-4bef-b623-356ceca01215/

Exploit#

https://wpscan.com/vulnerability/48250628-9b81-4bef-b623-356ceca01215/

History#

Version 12026-09-02Record published in the CVE List.

Published

Published: 2026-09-02
Last modified: 2026-09-02

Vendor information

Vendor: Not stated
Product: Ajaxify Comments

Score

5.4 Medium

EPSS

less than 1%, Very Low

Estimated chance of exploitation in the next 30 days. EPSS percentile: 20.1.

KEV

Not listed in the CISA Known Exploited Vulnerabilities catalog.

Impact

Not classified

Action

No specific action is recorded in the source data. Check the references for vendor guidance.

Affected Systems

Vulnerable
< 3.2
Fixed
3.2

Scoring System

CVSS v4.0

Not available

CVSS v3.1

5.4 Medium

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Metric breakdown
Attack Vector	Network
Attack Complexity	Low
Privileges Required	None
User Interaction	Required
Scope	Unchanged
Confidentiality	Low
Integrity	Low
Availability	None

CVSS v3.0

Not available

CVSS v2

Not available

Source: CVE List v5 (record); CISA KEV (kev, action); FIRST EPSS (epss).