Security readout for executives and security teams
Plain-English summary
CVE-2024-51652 affects the WordPress Skip To plugin through version 2.0.0. A malicious site could trick a user into making an unwanted request that stores script in the WordPress site. Impact depends on where that script runs, but the CVSS rating is high.
Executive priority
Treat as high priority only where the plugin is installed. The issue can create persistent browser-side compromise, but available sources do not show known exploitation or name a fixed release.
Technical view
The sources describe a CSRF weakness leading to stored XSS in marckocher Skip To <= 2.0.0, tracked as CWE-352. CVSS 3.1 is 7.1 with network attack vector, low complexity, no attacker privileges, required user interaction, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress sites with the Skip To plugin installed at version 2.0.0 or earlier. The source bundle does not provide install base, fixed version, storage location, or required victim role.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. Exploitation requires user interaction according to CVSS, consistent with a CSRF-to-stored-XSS scenario.
Researcher notes
Evidence is thin: the bundle provides CVE metadata, Patchstack reference, CVSS, and affected version range, but not the vulnerable parameter, nonce behavior, proof, or patch details. Avoid assuming exploitability beyond CSRF leading to stored XSS.
Mitigation direction
Inventory WordPress sites for the Skip To plugin and installed version.
Check Patchstack and vendor guidance for a fixed or recommended version.
If no safe version is confirmed, disable or remove the plugin temporarily.
Restrict administrative access and reinforce CSRF protections where supported.
Monitor affected sites for unexpected script content or page changes.
Validation and detection
Confirm whether each WordPress site has Skip To installed and active.
Flag any Skip To version 2.0.0 or earlier for remediation.
Review plugin-managed settings or content for unexpected script entries.
Check security monitoring for unusual WordPress admin actions.
Document remediation status and remaining sites awaiting vendor guidance.
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-352: 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-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.