Advanced Database CleanerWordPress extension · Sigmaplugin
CVE-2021-24141
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 · uneditedUnvaludated input in the Advanced Database Cleaner plugin, versions before 3.0.2, lead to SQL injection allowing high privilege users (admin+) to perform SQL attacks.
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 confidenceSQL injection vulnerability in the Advanced Database Cleaner WordPress plugin versions prior to 3.0.2, caused by unvalidated input that allows authenticated administrators to execute arbitrary SQL commands.
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
Advanced Database CleanerWordPress extension
< 3.0.2CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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.
-
Check if Advanced Database Cleaner plugin is installedIn WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'Advanced Database Cleaner' or 'Sigmaplugin Advanced Database Cleaner' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'advanced-database-cleaner' or similar.Affected if The plugin is not found in the installed plugins list or directory.
-
Identify the installed plugin versionIn WordPress admin, click on the plugin name in the Plugins list to view its details, which typically display the version number. Alternatively, check the main plugin PHP file (usually found in the plugin folder under wp-content/plugins/) for a version constant or header comment.Affected if The version displayed is any version number less than 3.0.2 (e.g., 3.0.1, 3.0.0, 2.x.x, etc.).
-
Verify the vulnerable code path existsExamine the plugin's PHP files for the SQL query execution functions (such as $wpdb->prepare, $wpdb->query, or direct query strings) that handle user input without proper sanitization, particularly in files related to database cleaning or optimization features.Affected if The plugin code contains unsanitized SQL queries that accept input from admin-side parameters without using $wpdb->prepare() or equivalent escaping.
A user is affected if the Advanced Database Cleaner plugin is installed with a version lower than 3.0.2 and the vulnerable SQL injection code path is present in the installation.
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 data3.0.2
Update Advanced Database Cleaner plugin to version 3.0.2 or later to patch the SQL injection vulnerability.
Fix this in Advanced Database Cleaner
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24141 — 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-2021-24141 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