Security readout for executives and security teams
Plain-English summary
Admin Cleanup for WordPress through version 1.0.2 has a high-severity issue where a user can be tricked into causing malicious content to be saved in the site. That stored script could later run in a browser. Business urgency depends on whether the plugin is installed on public WordPress sites.
Executive priority
Treat as a high-priority WordPress plugin exposure check. It is not confirmed as exploited in the provided sources, but stored XSS on administrative workflows can create meaningful site integrity and account-risk concerns.
Technical view
The CVE describes CSRF leading to stored XSS in Matt Gibbs Admin Cleanup, package admin-cleanup, through <= 1.0.2. CVSS 3.1 is 7.1 with network attack vector, low complexity, no attacker privileges, required user interaction, and changed scope.
Likely exposure
Likely exposure is limited to WordPress sites with the Admin Cleanup plugin installed at version 1.0.2 or earlier. The source bundle does not identify affected CPEs, install counts, or hosted service exposure.
Exploitation context
CISA KEV status is false, and the provided sources do not state active exploitation. The CVSS vector indicates an attacker needs user interaction but no prior privileges. Do not assume exploitation without local evidence.
Researcher notes
Evidence is sparse beyond the CVE record and Patchstack entry. The affected range is stated as through <= 1.0.2, but the bundle does not provide a patched version, proof-of-concept details, or exploitation telemetry.
Mitigation direction
Inventory WordPress sites for the admin-cleanup plugin.
If installed at <= 1.0.2, prioritize remediation review.
Check vendor, WordPress, or Patchstack guidance for a fixed release.
Disable or remove the plugin if it is not operationally required.
Limit administrative browsing and plugin management to trusted workflows.
Validation and detection
Confirm whether Admin Cleanup is installed on each WordPress site.
Record installed plugin version and compare against <= 1.0.2.
Review vendor or Patchstack advisory status before closing remediation.
Check site content and admin-facing pages for unexpected stored scripts.
Review logs for suspicious authenticated admin activity around the publish date.
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.