dbcve.org
Optimize Database After Deleting RevisionsWordPress extension · Cagewebdev

CVE-2023-25980

HIGH · 8.8 CVSS v3.1 Published 2023-10-04
Fix available
A fix is available. Upgrade to after 5.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in CAGE Web Design | Rolf van Gelder Optimize Database after Deleting Revisions plugin <= 5.1 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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Optimize Database after Deleting Revisions WordPress plugin versions 5.1 and below. The plugin lacks proper anti-CSRF tokens (nonces) on its administrative forms and actions, allowing authenticated administrators to unknowingly execute unintended database optimization operations when visiting malicious sites while logged in.

MitigationImplement WordPress nonces on all plugin forms and AJAX actions, verify nonces on form handlers, and set SameSite attribute on session cookies.

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
Optimize Database After Deleting RevisionsWordPress extension
Affected:<= 5.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin installation
    Navigate to WordPress admin > Plugins and confirm 'Optimize Database after Deleting Revisions' by Cagewebdev is installed and activated, or check the plugin directory wp-content/plugins/ for a folder containing the plugin files
    Affected if plugin is present and activated in WordPress
  2. Determine installed version
    In WordPress admin > Plugins page, click on the plugin name to view version details, or open the main plugin PHP file and locate the 'Version:' field in the plugin header comment block
    Affected if version is 5.1 or lower (the vulnerable range)
  3. Inspect code for nonce implementation
    Examine the main plugin PHP files that handle form submissions and AJAX actions. Search for WordPress nonce functions such as wp_verify_nonce, check_admin_referer, wp_create_nonce, or wp_nonce_field. These functions should be present on all administrative forms and AJAX handlers
    Affected if nonce verification functions are missing from the plugin's form handling code

Environment is affected if the Cagewebdev Optimize Database After Deleting Revisions plugin is installed at version 5.1 or below, or if the plugin code lacks proper nonce verification on its administrative forms and AJAX actions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 5.1
Interim mitigation

Implement WordPress nonces on all plugin forms and AJAX actions, verify nonces on form handlers, and set SameSite attribute on session cookies.

Recommended fix Moderate confidence

Version 5.2 or later

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the 'Optimize Database after Deleting Revisions' plugin
  4. 4. Click 'Update now' if an update is available, or download the latest version from the WordPress plugin repository
  5. 5. Verify the updated version is greater than 5.1

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Optimize Database After Deleting Revisions Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25980 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-25980 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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