Skip to main content
EPSS 0.3%top 81%

CVE-2026-2811: CWE-113 Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting') in Ajaxify Comments

0
Medium
VulnerabilityCVE-2026-2811cvecve-2026-2811cwe-113
Published: 09/02/2026 (09/02/2026, 14:25:51 UTC)
Source: CVE Database V5
Product: 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.

CVSS v3.1

Score 5.4medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Affected software

Ajaxify Comments

Affected versions
>=0 <3.2

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/07/2026, 13:52:24 UTC

Technical Analysis

CVE-2026-2811 describes an HTTP header injection vulnerability in the Ajaxify Comments WordPress plugin prior to version 3.2. The issue arises from insufficient input sanitization and output escaping of user-supplied data, enabling unauthenticated attackers to inject arbitrary HTTP headers. This vulnerability is categorized under CWE-113 (Improper Neutralization of CRLF Sequences in HTTP Headers), commonly known as HTTP Response Splitting. The vulnerability has a CVSS 3.1 base score of 5.4, reflecting medium severity with network attack vector, low attack complexity, no privileges required, and requiring user interaction.

Potential Impact

Successful exploitation allows unauthenticated attackers to inject arbitrary HTTP headers, which can lead to HTTP response splitting attacks. This may enable attackers to manipulate web responses, potentially causing security issues such as web cache poisoning or cross-site scripting via crafted responses. The confidentiality and integrity impacts are low, and availability is not affected.

Mitigation Recommendations

No official patch or remediation is currently confirmed for this vulnerability. Users should monitor the vendor's advisory for updates and apply any official fixes once available. Until then, consider implementing input validation and output escaping as a temporary mitigation if possible.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
WPScan
Date Reserved
2026-02-19T15:54:12.930Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6a9834bbacd9273b49595b36

Added to database: 09/02/2026, 14:37:47 UTC

Last enriched: 09/07/2026, 13:52:24 UTC

Last updated: 10/16/2026, 06:48:16 UTC

Views: 70

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses