Database Backup and check Tables Automated With Scheduler 2024 <= 2.35 - Authenticated (Administrator+) Sensitive Information Exposure
Strategic Overview
- Status
- Patched in 2.36
- Affected Version
<= 2.35- CVSS
- 7.2High
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2024-13911
At a glance
CVE-2024-13911 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Database Backup and Table Integrity Check with Automated Scheduling WordPress plugin, affecting versions <= 2.35. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 2.36; sites on affected versions should update now. Disclosed February 2025, reported by sterva.
Vulnerability Overview
The Database Backup and check Tables Automated With Scheduler 2024 plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.35 via the /dashboard/backup.php file. This makes it possible for authenticated attackers, with Administrator-level access and above, to extract sensitive data including full database credentials.
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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Database Backup and Table Integrity Check with Automated Scheduling <= 2.35 takes an account at Administrator level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Database Backup and Table Integrity Check with Automated Scheduling the fix is 2.36: builds <= 2.35 are affected, anything from 2.36 onward is not.
Remediation
Update to version 2.36, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: Database Backup and Table Integrity Check with Automated Scheduling 2.36 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in Database Backup and Table Integrity Check with Automated Scheduling
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C