<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Oct 2026 12:58:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-2717 — HTTP Headers &lt;= 1.19.2 - Authenticated (Administrator+) CRLF Injection via Custom Header Values</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-2717</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; zinoui HTTP Headers&lt;/p&gt;
&lt;p&gt;The HTTP Headers plugin for WordPress is vulnerable to CRLF Injection in all versions up to, and including, 1.19.2. This is due to insufficient sanitization of custom header name and value fields before writing them to the Apache .htaccess file via `insert_with_markers()`. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary newline characters and additional Apache directives into the .htaccess configuration file via the &amp;#39;Custom Headers&amp;#39; settings, leading to Apache configuration parse errors and potential site-wide denial of service.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; zinoui HTTP Headers&lt;/p&gt;
&lt;p&gt;The HTTP Headers plugin for WordPress is vulnerable to CRLF Injection in all versions up to, and including, 1.19.2. This is due to insufficient sanitization of custom header name and value fields before writing them to the Apache .htaccess file via `insert_with_markers()`. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary newline characters and additional Apache directives into the .htaccess configuration file via the &amp;#39;Custom Headers&amp;#39; settings, leading to Apache configuration parse errors and potential site-wide denial of service.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-2717</guid>
    </item>
  </channel>
</rss>
