CVE-2025-22516: WordPress Metadata SEO plugin <= 2.3 - Cross Site Scripting (XSS) vulnerability
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in hpinfosys Metadata SEO metadata-seo allows Stored XSS.This issue affects Metadata SEO: from n/a through <= 2.3.
Security readout for executives and security teams
Plain-English summary
A WordPress SEO plugin can store unsafe user-supplied content that later runs in another user's browser. This could let a low-privileged authenticated attacker affect administrators or editors who view the content. The business risk is site integrity, account misuse, and trust damage, but sources do not show active exploitation.
Executive priority
Treat as a near-term web application hygiene issue, especially on public WordPress sites with multiple content users. It is not evidenced as actively exploited, but stored XSS can become serious if administrators are targeted.
Technical view
CVE-2025-22516 is a stored XSS issue in hpinfosys Metadata SEO for WordPress, reported for versions through 2.3. CVSS 3.1 is 6.5 with network access, low attack complexity, low privileges required, user interaction required, and changed scope. The source bundle maps this to CWE-79.
Likely exposure
Exposure is likely limited to WordPress sites running the Metadata SEO plugin at version 2.3 or earlier. Risk rises where untrusted or numerous low-privileged users can create or modify plugin-managed metadata viewed by higher-privileged users.
Exploitation context
The CVE is not listed as KEV in the source bundle, and no cited source states active exploitation. The vulnerability requires an authenticated low-privileged attacker and a victim interaction path, consistent with stored XSS impact rather than unauthenticated server compromise.
Researcher notes
Evidence is incomplete on fixed-version availability. The narrative source says versions through 2.3 are affected, while the structured affected entry in the bundle is sparse; validate by plugin slug and installed version rather than relying only on CPE data.
Mitigation direction
Inventory WordPress sites for the Metadata SEO plugin and installed version.
Check vendor and Patchstack guidance for a fixed release or mitigation.
Upgrade if a vendor-supported fixed version is available.
If no fix is available, disable or remove the plugin where business impact allows.
Limit untrusted low-privileged WordPress accounts until remediation is complete.
Validation and detection
Confirm whether each WordPress instance uses the metadata-seo plugin.
Record plugin version and compare it with the through-2.3 affected range.
Review plugin-managed metadata for unexpected script-like markup.
Verify metadata fields encode user input correctly in a staging environment.
Confirm remediation by retesting affected workflows after update, removal, or disablement.
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.
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.
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.
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.