Head Meta Data <= 20250327 - Authenticated (Author+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 20251118
- Affected Plugin
- Head Meta Data
- Affected Version
<= 20250327- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2025-66081
At a glance
CVE-2025-66081 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Head Meta Data WordPress plugin, affecting versions <= 20250327. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 20251118; sites on affected versions should update now. Disclosed December 2025, reported by Athiwat Tiprasaharn (Jitlada).
Vulnerability Overview
The Head Meta Data plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 20250327 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Head Meta Data <= 20250327 takes an account at Author level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Head Meta Data the fix is 20251118: builds <= 20250327 are affected, anything from 20251118 onward is not.
Remediation
Update to version 20251118, or a newer patched version
How does WordSec protect against this?
An attacker needs Author access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Head Meta Data 20251118 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C