Ajaxify Comments < 3.2 - Unauthenticated HTTP Header Injection
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Unknown | Ajaxify Comments | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Wordpress-extensions | Ajaxify Comments |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.275% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wordpress-extensions
Wordpress-extensions ajaxify Comments |
|
| Vendors & Products |
Wordpress-extensions
Wordpress-extensions ajaxify Comments |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Ajaxify Comments < 3.2 - Unauthenticated HTTP Header Injection | |
| Weaknesses | CWE-113 | |
| References |
| |
| Metrics |
cvssV3_1
|