Simple Revisions DeleteWordPress extension · B Website
CVE-2024-30482
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 Brice CAPOBIANCO Simple Revisions Delete.This issue affects Simple Revisions Delete: from n/a through 1.5.3.
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 Simple Revisions Delete WordPress plugin allows attackers to trick authenticated administrators into performing unintended delete operations via maliciously crafted requests. The plugin lacks proper nonce validation on sensitive actions, enabling unauthorized revision deletion.
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
Simple Revisions DeleteWordPress extension
<= 1.5.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.
-
Confirm plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Simple Revisions Delete' by B Website, or check the /wp-content/plugins/ directory for a folder named 'simple-revisions-delete' or similar.Affected if The Simple Revisions Delete plugin by B Website is installed.
-
Check installed versionIn the Plugins list, find the Simple Revisions Delete entry and note the version number displayed below the plugin name, or inspect the plugin's main PHP file for the 'Version' header in the plugin comment block.Affected if The installed version is 1.5.3 or lower.
-
Inspect delete action handlers for nonce validationLocate the main plugin PHP file and search for functions handling revision deletion (keywords: 'delete', 'revision', 'trash'). Examine these functions to see if they call wp_verify_nonce, check_admin_referer, or wp_nonce_field before processing deletion.Affected if No nonce verification (wp_verify_nonce, check_admin_referer) is found in delete action handlers.
-
Check AJAX endpoints for nonce verificationSearch the plugin code for add_action calls registering AJAX handlers (wp_ajax_). For each AJAX action related to deletion, verify the callback function includes nonce validation before processing.Affected if AJAX-based delete actions lack nonce validation logic.
-
Verify form submissions include nonce fieldsSearch for form generation code (keywords: form, input, submit) in the plugin. Check if forms that trigger deletion actions include nonce fields (wp_nonce_field) as hidden inputs.Affected if Deletion forms do not contain nonce fields as hidden inputs.
A user is affected if they have Simple Revisions Delete version 1.5.3 or lower installed and the plugin's delete operations lack proper nonce validation in their code.
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 dataImplement WordPress nonces (wp_nonce_field/check_admin_referer) on all form submissions and AJAX actions within the plugin, and validate these nonces server-side before processing any deletion requests.
Fix this in Simple Revisions Delete
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-2024-30482 — 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-2024-30482 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