Wp Clean UpWordPress extension · Wp Clean Up Project
CVE-2023-25034
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 BoLiQuan WP Clean Up plugin <= 1.2.3 versions.
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 BoLiQuan WP Clean Up plugin versions 1.2.3 and below. Attackers can craft malicious requests that trick authenticated administrators into performing unintended actions, such as deleting content or modifying plugin settings, without their consent.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp Clean UpWordPress extension
<= 1.2.3CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Verify WP Clean Up plugin is installedAccess your WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'WP Clean Up' or 'WP Clean Up Project Wp Clean Up' in the list of installed plugins.Affected if The plugin appears in the installed plugins list.
-
Check the installed version numberIn the plugins list, locate the WP Clean Up plugin and note the version number displayed beneath the plugin name. Compare this version against the affected range of 1.2.3 and below.Affected if The displayed version is 1.2.3 or any version lower than 1.2.3.
-
Confirm the plugin is activeIn the plugins list, verify whether WP Clean Up shows as 'Active' under the plugin status column, or check the plugin settings page to confirm it is currently enabled.Affected if The plugin is active and the version is at or below 1.2.3.
-
Identify state-changing actionsReview the plugin settings and functionality to determine which actions are available, such as content deletion or configuration changes. These are the actions that could be triggered via CSRF.Affected if The plugin is active and exposes any administrative functions that modify data or settings without requiring re-authentication.
Your environment is affected if the WP Clean Up plugin is installed, active, and running at version 1.2.3 or lower, allowing unauthenticated or authenticated administrators to unknowingly trigger unintended actions via malicious requests.
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 the WP Clean Up plugin to the latest version once available, or disable the plugin until a patched version can be deployed. Additionally, implement anti-CSRF tokens (nonces) on all state-changing actions within the plugin.
Fix this in Wp Clean Up
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25034 — 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-2023-25034 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