Advanced Database CleanerWordPress extension · Sigmaplugin
CVE-2023-49764
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Younes JFR. Advanced Database Cleaner.This issue affects Advanced Database Cleaner: from n/a through 3.1.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 confidenceSQL injection vulnerability in Advanced Database Cleaner plugin allows attackers to inject malicious SQL commands via unsanitized input parameters. The vulnerability exists in versions through 3.1.2 and stems from improper neutralization of special elements in database queries.
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.1.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.
-
Identify the installed Advanced Database Cleaner versionNavigate to WordPress admin > Plugins > Advanced Database Cleaner and view the version number displayed, or check the plugin header in wp-content/plugins/advanced-db-cleaner/readme.txtAffected if The displayed version is 3.1.2 or any lower version number
-
Locate the plugin version file directlyAccess the site via FTP or file manager and open /wp-content/plugins/advanced-db-cleaner/readme.txt, then locate the 'Stable tag' field in the file headerAffected if The stable tag entry shows version 3.1.2 or lower
-
Compare your version against the affected rangeReview the version number found against the affected range: all versions through and including 3.1.2Affected if Your installed version is 3.1.2 or earlier (any version <= 3.1.2)
-
Inspect database query execution pointsIf you have access to the plugin source code, examine PHP files in the plugin directory for direct SQL query construction using $wpdb->prepare or raw $wpdb->query calls without proper escapingAffected if Queries use user-supplied input directly in SQL strings without parameterized binding
You are affected if the installed Advanced Database Cleaner plugin version is 3.1.2 or any earlier version, since all versions through 3.1.2 contain the SQL injection 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 dataUpgrade to a patched version that implements proper input sanitization and uses parameterized queries/prepared statements for all database operations. If no patch is available, validate and sanitize all user inputs before using them in SQL queries.
Fix this in Advanced Database Cleaner
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49764 — 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-49764 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