Skip to content
Laskyr

Plugins · head-meta-data · data as of 2026-11-04

Is Head Meta Data safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (20260810)

As of 2026-11-04. 2 issues are on record for older versions; version 20260105 or newer fixes all of them that state a fix.

Latest version
20260810
Last updated
2026-08-10
Active installs
10,000+
Known issues on record
2
Unpatched in latest
0
Tested up to WP
7.1.4 · PHP 5.6.20+

Adds a custom set of <meta> tags to the <head> section of all posts & pages. — by Jeff Starr

What to do

  1. Update to the latest version (20260810). Anything older than 20260105 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get head-meta-data --field=version shows what you run; wp plugin update head-meta-data updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 6.4 CVE-2026-0608 · published 2026-01-20

Stored cross-site scripting (XSS) in Head Meta Data (20251118 and older)

Affected
20251118 and older
Fixed in
20260105 *
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber)
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The Head Meta Data plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'head-meta-data' post meta field in all versions up to, and including, 20251118 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

NVD CVE-2026-0608Wordfence advisoryCode change (fix)

medium 5.9 CVE-2025-66081 · published 2025-11-21

Stored cross-site scripting (XSS) in Head Meta Data (20250327 and older)

Affected
20250327 and older
Fixed in
20251118
Access needed (per CVSS)
Needs an admin-level account; someone on the site has to click a link or open a page
Range from
CVE record (the advisory publisher) · score by Patchstack
Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Jeff Starr Head Meta Data head-meta-data allows Stored XSS.This issue affects Head Meta Data: from n/a through <= 20250327.

NVD CVE-2025-66081Patchstack advisory

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Head Meta Data vulnerability status badge
<a href="https://laskyr.com/plugins/head-meta-data"><img src="https://laskyr.com/plugins/head-meta-data/badge.svg" alt="Head Meta Data vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit