Ajaxify Comments < 3.2 - Unauthenticated HTTP Header Injection (CVE-2026-2811) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-2811

Ajaxify Comments < 3.2 - Unauthenticated HTTP Header Injection

Answer in brief

CVE-2026-2811 records a Unknown severity vulnerability in Ajaxify Comments < 3.2 - Unauthenticated HTTP Header Injection. The current sources do not mark it as known exploited. The current feed maps Unknown/Ajaxify Comments (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 2, 2026Updated Sep 2, 2026Source checked Sep 2, 2026First seen by HOL Sep 2, 2026Material review Sep 2, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Unknown/Ajaxify Comments (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Unknown/Ajaxify Commentsgeneric	>=0 <3.2	3.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for Unknown/Ajaxify Comments.
Review the reported fix. Update Unknown/Ajaxify Comments to 3.2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 2, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 2, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 2, 2026

Sources and claim methodology

Source referencewpscan.com

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.