Bulk Comment RemoveWordPress extension · Supremo
CVE-2023-48330
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 Mike Strand Bulk Comment Remove allows Cross Site Request Forgery.This issue affects Bulk Comment Remove: from n/a through 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 Bulk Comment Remove WordPress plugin allows attackers to trick authenticated administrators into performing unwanted comment removal actions by exploiting the lack of anti-CSRF token validation on state-changing requests.
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
Bulk Comment RemoveWordPress extension
<= 2.0CVSS 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.
-
Locate the plugin installationCheck your WordPress wp-content/plugins/ directory for a folder named 'supremo-bulk-comment-remove' or similar. Alternatively, go to WordPress Admin > Plugins and look for 'Supremo Bulk Comment Remove' in the installed plugins list.Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in the WordPress plugins list
-
Determine the installed versionIf the plugin is installed, open the main plugin PHP file (usually named like bulk-comment-remove.php or similar in the plugin folder) and locate the version header comment at the top. Alternatively, check the plugin row in WordPress Admin > Plugins which typically displays the version number.Affected if The displayed version number is 2.0 or lower (e.g., 2.0, 1.9, 1.0)
-
Verify the plugin is activatedIn WordPress Admin > Plugins, check if the Supremo Bulk Comment Remove plugin shows as 'Active' rather than 'Inactive' or 'Must Use'.Affected if The plugin is currently activated on the WordPress site
-
Inspect for CSRF protection in codeExamine the PHP files in the plugin folder, specifically any files handling comment removal actions or AJAX endpoints. Search for wp_verify_nonce, wp_create_nonce, or check_admin_referer function calls that validate request authenticity before processing comment removal.Affected if No nonce validation (wp_verify_nonce, check_admin_referer) is found in files that handle comment removal state-changing operations, meaning requests lack CSRF protection
You are affected if the Supremo Bulk Comment Remove plugin is installed, activated, and the version is 2.0 or lower with no nonce validation present in the comment removal 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_create_nonce/wp_verify_nonce) on all comment removal action forms and AJAX endpoints to validate request authenticity and bind tokens to user sessions.
Fix this in Bulk Comment Remove
Scoped from the published advisory
- 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-2023-48330 — 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-48330 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