Cyber Resilience

CVE-2024-13911

High

Published: 01 March 2025

Published
01 March 2025
Modified
15 April 2026
KEV Added
Patch
CVSS Score v3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0020 42.0th percentile
Risk Priority 15 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2024-13911 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor (CWE-200) vulnerability in Wordpress (inferred from references). Its CVSS base score is 7.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 42.0th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified are NIST 800-53 AU-13 (Monitoring for Information Disclosure) and SI-15 (Information Output Filtering).

Deeper analysis

CVE-2024-13911 is a sensitive information exposure vulnerability (CWE-200) affecting the Database Backup and check Tables Automated With Scheduler 2024 plugin for WordPress in all versions up to and including 2.35. The issue resides in the /dashboard/backup.php file, where sensitive data, including full database credentials, can be extracted. It has a CVSS v3.1 base score of 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), indicating high severity due to network accessibility, low attack complexity, and significant impacts on confidentiality, integrity, and availability.

Authenticated attackers with Administrator-level access or higher can exploit this vulnerability remotely without user interaction. By accessing the vulnerable /dashboard/backup.php endpoint, they can retrieve exposed sensitive information such as complete database credentials, potentially enabling further compromise of the WordPress site's backend database.

The provided references point to specific lines (62-66) in the plugin's trunk/dashboard/backup.php file on the WordPress plugin trac repository, highlighting the exact location of the exposure in the source code. No additional advisory details on patches or mitigations are specified beyond identifying the vulnerable versions up to 2.35.

EU & UK References

Vulnerability details

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…

more

access and above, to extract sensitive data including full database credentials.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
Why these techniques?

Vulnerability directly exposes database credentials in a web-accessible file on a public-facing WordPress plugin, enabling exploitation via T1190 and credential retrieval from files via T1552.001.

Confidence: HIGH · MITRE ATT&CK Enterprise v18.1

CVEs Like This One

CVE-2025-25729Shared CWE-200
CVE-2024-13609Shared CWE-200
CVE-2025-22961Shared CWE-200
CVE-2026-30928Shared CWE-200
CVE-2025-27784Shared CWE-200
CVE-2026-2268Shared CWE-200
CVE-2024-13796Shared CWE-200
CVE-2025-25975Shared CWE-200
CVE-2024-12142Shared CWE-200
CVE-2025-25951Shared CWE-200

Affected Assets

Wordpress
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly mitigates the vulnerability by requiring identification, reporting, and remediation of the flaw exposing database credentials in the plugin's backup.php file.

prevent

Prevents sensitive database credentials from being exposed by filtering information output from the vulnerable /dashboard/backup.php endpoint.

detect

Monitors the system for unauthorized disclosures of sensitive information, such as database credentials extracted via the plugin's vulnerable file.

References