WordPress plugin · Updated daily · Source: Wordfence Intelligence

HTTP Headers vulnerabilities: affected versions and fixes

HTTP Headers has 40,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

HTTP Headers at a glance

  • 7 publicly disclosed vulnerabilities, 1 of them rated High or Critical. The most recent was disclosed on Apr 21, 2026.
  • Ranked #811 by popularity on WordPress.org (40,000+ active installs).
  • The latest version is 1.19.6 (released Oct 16, 2026). The most recent security fix shipped in 1.19.5.
  • 1 vulnerability has no fix yet. Check the list below to see whether it affects how you use the plugin.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your HTTP Headers version

Enter the HTTP Headers version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “HTTP Headers”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “HTTP Headers”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (1.19.6). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known HTTP Headers vulnerabilities

  • HTTP Headers <= 1.19.5 - Authenticated (Administrator+) CRLF Injection via Custom Header Values

    Other weakness · CVE-2026-2717

    Affected versions: ≤ 1.19.5

    Fixed in: No fix yet

    Severity: Medium 5.5 · Disclosed Apr 21, 2026

  • HTTP Headers <= 1.19.4 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'Custom Headers' Plugin Setting

    Cross-site scripting (XSS) · CVE-2026-1379

    Affected versions: ≤ 1.19.4

    Fixed in: 1.19.5

    Severity: Medium 4.4 · Disclosed Apr 21, 2026

  • HTTP Headers <= 1.19.2 - Authenticated (Administrator+) External Control of File Name or Path to RCE via 'hh_htpasswd_path' and 'hh_www_authenticate_user' Parameters

    Remote code execution · CVE-2026-4132

    Affected versions: ≤ 1.19.2

    Fixed in: 1.19.3

    Severity: High 7.2 · Disclosed Apr 21, 2026

  • HTTP Headers <= 1.18.11 - Server-Side Request Forgery

    Server-side request forgery (SSRF) · CVE-2023-37978

    Affected versions: ≤ 1.18.11

    Fixed in: 1.19.0

    Severity: Medium 5.5 · Disclosed Jul 13, 2023

  • HTTP Headers <= 1.18.11 - Authenticated (Administrator+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2023-37874

    Affected versions: ≤ 1.18.11

    Fixed in: 1.19.0

    Severity: Medium 4.4 · Disclosed Jul 10, 2023

  • HTTP Headers <= 1.18.10 - Authenticated(Administrator+) Remote Code Execution

    Remote code execution · CVE-2023-1208

    Affected versions: ≤ 1.18.10

    Fixed in: 1.18.11

    Severity: Medium 6.6 · Disclosed Jun 19, 2023

  • HTTP Headers <= 1.18.8 - Authenticated(Administrator+) SQL Injection

    SQL injection · CVE-2023-1207

    Affected versions: ≤ 1.18.8

    Fixed in: 1.18.9

    Severity: Medium 6.6 · Disclosed Apr 24, 2023

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Apr 21, 2026.

Most common weaknesses in HTTP Headers

Cross-site scripting (XSS)

2 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Remote code execution

2 issues

An attacker can run code of their choice on your server. This is the most dangerous kind: it usually means a full takeover of the site.

Server-side request forgery (SSRF)

1 issue

Your server can be made to send requests to other systems on the attacker’s behalf, including internal ones.

Frequently asked questions

Is HTTP Headers safe to use?

HTTP Headers is a well-known plugin with 40,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (1.19.6) and turn on automatic updates. That said, 1 issue has no fix yet, so check the list below.

How do I find which version of HTTP Headers my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesHTTP Headers on WordPress.org