CVE-2024-51592: WordPress Meta Store Elements plugin <= 1.0.9 - Cross Site Scripting (XSS) vulnerability
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Mystical Themes Meta Store Elements meta-store-elements allows DOM-Based XSS.This issue affects Meta Store Elements: from n/a through <= 1.0.9.
Security readout for executives and security teams
Plain-English summary
CVE-2024-51592 is a DOM-based cross-site scripting issue in the WordPress Meta Store Elements plugin. If abused, it could let an attacker influence what a user sees or does in their browser. The source rates it medium, and exploitation requires a logged-in attacker and user interaction.
Executive priority
Treat this as a normal-priority WordPress remediation item, not an emergency, unless the plugin is widely deployed on high-value public sites. Prioritize inventory and update decisions because the source does not confirm active exploitation.
Technical view
The issue is CWE-79 improper neutralization during page generation in Mystical Themes Meta Store Elements through version 1.0.9. CVSS 3.1 is 6.5 with network attack vector, low complexity, low privileges required, user interaction required, and changed scope.
Likely exposure
Exposure is limited to WordPress sites with Meta Store Elements installed at versions through 1.0.9. The supplied affected metadata is sparse and has no CPE, so asset inventory should verify plugin name, slug, and installed version directly.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates exploitation is plausible remotely but needs some privileges and a user interaction path.
Researcher notes
Evidence supports DOM-based XSS in Meta Store Elements through 1.0.9 with CVSS 6.5. The bundle does not provide payload details, fixed-version data, or exploitation telemetry. Avoid assuming broader Mystical Themes product impact.
Mitigation direction
Inventory WordPress sites for the meta-store-elements plugin.
Check vendor, WordPress, or Patchstack guidance for a fixed release.
Update the plugin if an official fixed version is available.
Disable or remove the plugin where it is not business-critical.
Restrict plugin administration to trusted users only.
Validation and detection
Confirm whether Meta Store Elements is installed on each WordPress site.
Record the installed plugin version and compare against <= 1.0.9.
Review whether exposed pages use plugin-generated DOM content.
Check Patchstack or vendor records for current remediation status.
Monitor for suspicious script-injection reports without attempting exploitation.
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.