Lucene search
+L

5 matches found

NVD
NVD
added 2026/09/02 3:17 p.m.2 views

CVE-2026-2811

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

5.4CVSS
SaveExploits0References1
CVE
CVE
added 2026/09/02 2:25 p.m.7 views

CVE-2026-2811

The Ajaxify Comments WordPress plugin before version 3.2 is affected by an HTTP Header Injection vulnerability caused by insufficient input sanitization and output escaping on user-supplied data. Unauthenticated attackers can inject arbitrary HTTP headers, resulting in low confidentiality and int...

5.4CVSS6AI score
SaveExploits0References1
Vulnrichment
Vulnrichment
added 2026/09/02 2:25 p.m.4 views

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

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

5.4CVSS6AI score
SaveExploits0References1
EUVD
EUVD
added 2026/09/02 2:25 p.m.5 views

EUVD-2026-70050

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

5.4CVSS6AI score
SaveExploits0References1
Cvelist
Cvelist
added 2026/09/02 2:25 p.m.10 views

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

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

5.4CVSS
SaveExploits0References1
Rows per page
Query Builder