<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cpe:2.3:a:keep_backup_daily:keep_backup_daily:*:*:*:*:*:wordpress:*:* - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3akeep_backup_dailykeep_backup_dailywordpress/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Mon, 31 Aug 2026 17:58:26 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3akeep_backup_dailykeep_backup_dailywordpress/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Information Exposure in Keep Backup Daily WordPress Plugin</title><link>https://feed.craftedsignal.io/briefs/2026-08-keep-backup-daily-exposure/</link><pubDate>Mon, 31 Aug 2026 17:58:26 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-keep-backup-daily-exposure/</guid><description>The Keep Backup Daily plugin for WordPress before 2.1.4 contains a vulnerability allowing unauthenticated attackers to trigger database backups and retrieve them via predictable filenames.</description><content:encoded><![CDATA[<p>The Keep Backup Daily plugin for WordPress (versions prior to 2.1.4) is vulnerable to a sensitive information exposure flaw. This vulnerability allows an unauthenticated attacker to initiate a full MySQL database dump by invoking the <code>kbd_cron_process</code> parameter. The plugin generates backup files in the site's publicly accessible <code>uploads</code> directory. Because the naming convention for these backup files is partially predictable - based on the database name, a limited randomization factor, and the current Unix timestamp - attackers can enumerate and download these sensitive backups. This exposes the entire site database, including user credentials, configuration secrets, and other sensitive content. This vulnerability is critical for environments where the plugin is enabled, as it provides an automated pathway for total data exfiltration without requiring privileged access.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker performs reconnaissance to identify WordPress sites running the Keep Backup Daily plugin.</li>
<li>Attacker sends an unauthenticated HTTP GET/POST request to the target site using the <code>kbd_cron_process</code> parameter to trigger the backup generation script.</li>
<li>The plugin executes the backup routine, dumping the MySQL database into a file within the <code>/wp-content/uploads/</code> directory.</li>
<li>Attacker monitors the request or estimates the Unix timestamp at the time of execution.</li>
<li>Attacker iterates through possible filenames based on the database name and the predictable timestamp and random range.</li>
<li>Attacker attempts to download the generated backup file directly via standard web request.</li>
<li>Attacker successfully exfiltrates the complete database contents.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation leads to the complete exfiltration of the WordPress database. This includes sensitive data such as site administrator credentials, hashed user passwords, configuration files, and PII of registered users. The breach of this data provides an attacker with the necessary information to perform full account takeover or further compromise the hosting environment.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Patch the Keep Backup Daily plugin to version 2.1.4 or later immediately across all WordPress installations.</li>
<li>Deploy the provided Sigma rule to detect attempts to invoke the <code>kbd_cron_process</code> parameter from unauthenticated sources.</li>
<li>Audit web server logs for suspicious access patterns targeting the <code>/wp-content/uploads/</code> directory with file extensions indicative of database backups (e.g., .sql, .zip, .sql.gz).</li>
<li>Implement restrictions on the web server to prevent direct access to sensitive file types within the uploads directory.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>wordpress</category><category>vulnerability</category><category>web-application</category><category>data-exfiltration</category></item></channel></rss>