Skip to main content
VulnerabilityPublished

CVE-2026-2717: HTTP Headers (WordPress plugin) · CRLF Injection

Affects HTTP Headers (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
zinouiHTTP HeadersAffected
  • <=1.19.2
Fixed in–

AI-suggested

Until an official fix is released, restrict Administrator access to trusted users only and avoid using the 'Custom Headers' feature to add untrusted input. Monitor vendor channels for updates or patches addressing this vulnerability.

Description

CVE-2026-2717 is a medium severity vulnerability affecting the zinoui HTTP Headers WordPress plugin up to version 1.19.2. It involves improper neutralization of CRLF sequences, allowing authenticated administrators to inject newline characters and arbitrary Apache directives into the . htaccess file. This injection can cause Apache configuration parse errors and potentially lead to site-wide denial of service. The vulnerability arises from insufficient sanitization of custom header names and values before writing to the . htaccess file via the insert_with_markers() function. No official patch or remediation guidance is currently available.

References

Community reviews

Loading reviews…