CVE-2025-11497

Advanced Database Cleaner <= 3.1.6 - Cross-Site Request Forgery to Settings Manipulation

2025-10-24 00:00
Bao - BlueRock

Strategic Overview

Status
Patched in 3.1.7
Affected Version
<= 3.1.6
CVSS
4.3Medium
Weakness type
CWE-20 · Improper Input Validation
CVE
CVE-2025-11497
View all Advanced Database Cleaner – Optimize & Clean Database to Speed Up Site Performance vulnerabilities

At a glance

CVE-2025-11497 is a medium-severity Improper Input Validation vulnerability in the Advanced Database Cleaner WordPress plugin, affecting versions <= 3.1.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.7; sites on affected versions should update now. Disclosed October 2025, reported by Bao - BlueRock.

Vulnerability Overview

The Advanced Database Cleaner plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.1.6. This is due to missing or incorrect nonce validation on the aDBc_prepare_elements_to_clean() function. This makes it possible for unauthenticated attackers to alter the keep last setting via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE-2025-64357 is a duplicate of this issue.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-20: Improper Input Validation

Advanced Database Cleaner <= 3.1.6 carries this weakness at aDBc_prepare_elements_to_clean(), and reaching it takes a caller who can reach the endpoint. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.

The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. For Advanced Database Cleaner the fix is 3.1.7: builds <= 3.1.6 are affected, anything from 3.1.7 onward is not.

Remediation

Update to version 3.1.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Advanced Database Cleaner: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Advanced Database Cleaner 3.1.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C