# CVE-2026-4029: Database Backup for WordPress <= 2.5.2 - Missing Authorization to Unauthenticated Database Export

> Unauthenticated attackers can export database tables in WordPress Multisite environments, exposing sensitive information.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-p94x-gw9w-73f2

## What is CVE-2026-4029?

CVE-2026-4029 is a high-severity missing authorization vulnerability in wpengine Database Backup for WordPress, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Database Backup for WordPress plugin for WordPress is vulnerable to unauthorized database export in all versions up to, and including, 2.5.2. This is due to the plugin not properly enforcing the return value of its authorization check. This makes it possible for unauthenticated attackers to export database tables, leading to Sensitive Information Exposure. Note: This vulnerability is only exploitable in WordPress Multisite environments where the deprecated is_site_admin() function exists.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-4029 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4029 is a high-severity missing authorization vulnerability in wpengine Database Backup for WordPress, published on 14 May 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-4029 in the wild and no public exploit code.

Affected product: wpengine Database Backup for WordPress. 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-4029/ (Markdown: https://insights.sbomify.com/CVE-2026-4029/index.md)
```

## Sources

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

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