CVE-2025-23832
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in Matt Gibbs Admin Cleanup admin-cleanup allows Stored XSS.This issue affects Admin Cleanup: from n/a through <= 1.0.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the Admin Cleanup plugin allows authenticated administrators to be tricked into performing unintended actions that result in Stored XSS. The attacker can craft a malicious link that, when clicked by an authenticated admin, injects persistent malicious scripts into the admin-facing pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Admin Cleanup plugin is installedNavigate to your CMS plugin management interface and verify the Admin Cleanup plugin is present and activeAffected if The Admin Cleanup plugin is installed and active in the CMS
-
Identify the installed version of Admin CleanupView the plugin details or version information in your CMS plugin list, or check the plugin header in its main PHP fileAffected if The installed version is lower than the patched version (when released) or no version information is available
-
Inspect admin action forms for CSRF protectionView the source code of admin-facing forms in the Admin Cleanup plugin and check if anti-CSRF tokens or nonce fields are present in POST/GET requestsAffected if Forms performing admin actions lack CSRF token validation or use predictable/non-random tokens
-
Check for stored XSS in admin pagesReview the HTML source of admin dashboard pages and look for unexpected script tags, iframe elements, or event handlers in stored data fieldsAffected if Malicious JavaScript or HTML content is persistently stored and rendered in admin-facing pages without proper sanitization
-
Review admin action request headersUse browser developer tools or proxy to examine if admin actions in the plugin include SameSite cookies and CSRF token headersAffected if Admin actions do not validate origin headers or lack SameSite cookie protections
You are affected if Admin Cleanup plugin is installed AND the installed version lacks CSRF protection mechanisms on admin actions, allowing stored XSS injection through crafted links.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Admin Cleanup to the latest patched version once released. Until then, implement anti-CSRF tokens on admin actions and ensure all user inputs are properly sanitized before storage and output.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23832 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-23832 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data