# CVE-2026-75133: Keep Backup Daily WordPress Plugin < 2.1.4 Sensitive Information Exposure via kbd_cron_process

> Unauthenticated attackers can trigger and download full MySQL database dumps by exploiting a publicly accessible cron parameter in the Keep Backup Daily plugin.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-v523-g24m-hrq6

## What is CVE-2026-75133?

CVE-2026-75133 is a high-severity vulnerability in Fahad Mahmood Keep Backup Daily, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Keep Backup Daily plugin for WordPress before 2.1.4 contains a sensitive information exposure vulnerability that allows unauthenticated attackers to trigger a full MySQL database dump by accessing the publicly exposed `kbd_cron_process` parameter without authentication. Attackers can predict the partially predictable dump filename based on the database name, a limited random range, and the current Unix timestamp to download the generated backup from the publicly accessible uploads directory.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-75133?


## How do I fix CVE-2026-75133?

No fix has been published for CVE-2026-75133 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-75133 being exploited?

There is no known exploitation of CVE-2026-75133 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75133 and fix it if it is affected.

What it is: CVE-2026-75133 is a high-severity vulnerability in Fahad Mahmood Keep Backup Daily, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75133 in the wild and no public exploit code.

Affected product: Fahad Mahmood Keep Backup Daily. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-75133/ (Markdown: https://insights.sbomify.com/CVE-2026-75133/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-75133
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-75133
- OSV: https://osv.dev/vulnerability/CVE-2026-75133

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-75133/
Summaries are generated and may contain mistakes; the official description above is the record.