{"id":"CVE-2026-2811","aliases":["EUVD-2026-70050","GHSA-jxm3-h8qw-wgcx"],"status":"published","title":"Ajaxify Comments \u003c 3.2 - Unauthenticated HTTP Header Injection","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.","severity":{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-07","score":0.00275,"percentile":0.20053,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-113"],"published":"2026-09-02T14:25:51Z","modified":"2026-09-03T17:50:37Z","products":[{"vendor":"unknown","product":"ajaxify comments"}],"references":[{"url":"https://wpscan.com/vulnerability/48250628-9b81-4bef-b623-356ceca01215/","tags":["exploit","vdb-entry","technical-description"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-2811"},{"url":"https://wpscan.com/vulnerability/48250628-9b81-4bef-b623-356ceca01215"},{"url":"https://github.com/advisories/GHSA-jxm3-h8qw-wgcx"}],"sources":{"cve":[{"id":"CVE-2026-2811","title":"Ajaxify Comments \u003c 3.2 - Unauthenticated HTTP Header Injection","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.","status":"published","published":"2026-09-02T14:25:51.312Z","modified":"2026-09-02T14:57:35.38Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-113"],"updated_at":"2026-11-02T13:48:46.911326Z"}],"euvd":[{"id":"EUVD-2026-70050","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.","status":"published","published":"2026-09-02T14:25:51Z","modified":"2026-09-02T14:57:35Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T18:01:15.49101Z"}],"ghsa":[{"id":"GHSA-jxm3-h8qw-wgcx","title":"The Ajaxify Comments WordPress plugin before 3.2 is vulnerable to HTTP Header Injection due to...","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.","status":"published","published":"2026-09-02T15:34:49Z","modified":"2026-09-02T15:34:55Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","level":"medium"}],"cwes":["CWE-113"],"updated_at":"2026-11-02T15:11:17.291346Z"}],"nvd":[{"id":"CVE-2026-2811","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.","status":"published","published":"2026-09-02T15:17:38.27Z","modified":"2026-09-03T17:50:37.69Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-113"],"updated_at":"2026-11-02T14:12:43.399612Z"}]}}