CVE-2025-60223
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 · uneditedSubscriber Arbitrary File Deletion in WPBot Pro Wordpress Chatbot <= 13.6.5 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 · high confidenceThe WPBot Pro WordPress chatbot plugin versions 13.6.5 and earlier contains an arbitrary file deletion vulnerability that can be exploited by users with Subscriber-level privileges. The plugin fails to properly validate file deletion permissions, allowing any authenticated subscriber to delete arbitrary files on the server filesystem.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/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 WPBot Pro plugin versionIn WordPress admin, go to Plugins > Installed Plugins > WPBot Pro and check the Version number displayed. Alternatively, check the plugin header in wp-content/plugins/wpbot-pro/wpbot.php for the 'Version' comment tag.Affected if The installed version is 13.6.5 or any earlier version.
-
Confirm plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify that WPBot Pro is currently activated.Affected if The plugin is active and the version is 13.6.5 or earlier.
-
Check for subscriber-level user accountsIn WordPress admin, go to Users and review the list of existing user accounts. Look for any accounts with the Subscriber role.Affected if Subscriber-level accounts exist on the site and the vulnerable plugin version is installed and active.
-
Audit file deletion capabilitiesReview WordPress user roles and capabilities configuration. Confirm whether any subscriber-level accounts have been granted elevated permissions beyond standard subscriber capabilities, particularly any capability related to file operations or deletion.Affected if Subscriber role has been granted additional capabilities beyond the default, or if any authenticated user can access plugin functions that handle file deletion.
You are affected if WPBot Pro plugin version 13.6.5 or earlier is installed and active on your WordPress site, and subscriber-level user accounts exist that could potentially exploit this vulnerability.
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 WPBot Pro plugin to a version beyond 13.6.5 that patches this vulnerability. Until then, consider restricting or monitoring subscriber-level accounts and disabling the plugin if immediate patching is not possible.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60223 — 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-60223 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