LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0608: Head Meta Data <= 20251118 - Authenticated (Contributor+) Stored Cross-Site Scripting via Post Meta

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.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-0608 affects the WordPress Head Meta Data plugin. A logged-in user with Contributor-level access or higher could store malicious script in a page’s metadata. That script may run when others view the affected page. Business risk is highest on sites with many content contributors or weak account controls.

Executive priority

Treat as a moderate-priority web content risk. Prioritize sites with public traffic, many contributors, or sensitive admin sessions. This is not currently supported as actively exploited in the provided sources.

Technical view

The issue is stored cross-site scripting in the 'head-meta-data' post meta field, caused by insufficient input sanitization and output escaping. Versions up to and including 20251118 are listed as vulnerable. CVSS 3.1 is 6.4 with low privileges required, network attack vector, changed scope, and low confidentiality and integrity impact.

Likely exposure

WordPress sites using Head Meta Data versions up to 20251118, especially where Contributor, Author, Editor, or Administrator accounts are broadly assigned or compromised.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires authenticated Contributor-level access or higher, but no user interaction is required once a vulnerable page is viewed.

Researcher notes

Key evidence comes from the CVE record and Wordfence advisory. The WordPress Trac reference compares tag 20251118 to 20260105, suggesting a relevant code change, but validation should rely on vendor release guidance.

Mitigation direction

  • Update Head Meta Data to the latest available version after reviewing vendor guidance.
  • If immediate update is not possible, restrict Contributor-level and higher access.
  • Review and remove untrusted content from Head Meta Data post meta fields.
  • Disable the plugin temporarily if business impact allows and exposure is high.

Validation and detection

  • Inventory WordPress sites for the Head Meta Data plugin.
  • Confirm whether installed versions are up to and including 20251118.
  • Verify role assignments for Contributor-level and higher users.
  • Review relevant post metadata for suspicious or unexpected script content.
  • Confirm remediation by checking the installed plugin version after update.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0608 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.4Medium
CVSS 3.1 vector shape for CVE-2026-0608Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
specialkHead Meta Data0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.