CVE-2026-2811: Ajaxify Comments < 3.2 - Unauthenticated HTTP Header Injection

Published Sep 2, 2026
·
Updated

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.

Affected Software

1 affected component
WordPress Ajaxify Comments<3.2

Event History

Sep 2, 2026
CVE Published
via MITRE·02:25 PM
Data Sourced
via MITRE·02:25 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which installations are affected?

WordPress sites using Ajaxify Comments versions earlier than 3.2 are affected. The issue is in the plugin, not WordPress generally.

2

Does exploitation require an account or special privileges?

No. The vulnerability is described as exploitable by unauthenticated attackers, so no WordPress account or prior privileges are required. Exploitation does require user interaction according to the supplied CVSS vector.

3

What is the impact of successful exploitation?

An attacker can inject arbitrary HTTP headers because user-supplied data is not sufficiently sanitized and escaped. The provided severity vector indicates low confidentiality and integrity impact, with no availability impact.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203