Skip to main content
Menu
CVEs

Backup For WP WP Database Backup unauthenticated data exposure in backup functions

Affects the WP Database Backup plugin for WordPress, version 7.14 and earlier. Fixed in 7.15.

CVE-2026-129065Published , updated

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 7.15
Who is exposed
Not reported

Summary

Backup For WP's WP Database Backup plugin for WordPress has a missing authorization flaw that lets an attacker reach functions they should not be able to use. It can be exploited remotely, without logging in, and the impact is a high loss of confidentiality.

Written by a model

Original description

Missing Authorization vulnerability in Backup For WP WP Database Backup wp-database-backup allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Database Backup: from n/a through 7.14.

Who should check

Sites and hosts running the WP Database Backup WordPress plugin version 7.14 or earlier.

“WordPress WP Database Backup Plugin <= 7.14 is vulnerable”

patchstack.com

What to do

Upgrade to a fixed version: 7.15.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129065 (WordPress WP Database Backup plugin <= 7.14 - Broken Access Control vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129065 (entry last updated 2026-11-20):
Affected:
- Backup For WP WP Database Backup: fixed in 7.15
Fixed versions: 7.15.
Conditions (all must be true for the bug to be hit):
- WP Database Backup plugin version 7.14 or earlier (source: https://patchstack.com/database/wordpress/plugin/wp-database-backup/vulnerability/wordpress-wp-database-backup-plugin-7-14-broken-access-control-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129065 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129065 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/wp-database-backup/vulnerability/wordpress-wp-database-backup-plugin-7-14-broken-access-control-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129065
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129065"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 2

Questions about CVE-2026-129065

Is CVE-2026-129065 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The plugin has a broken access control flaw, so users can reach pages or perform actions they should not be allowed to. The advisory's example is viewing other people's data.

Source: patchstack.com

Which versions are affected by CVE-2026-129065?

wp-database-backup: through 7.14 (fixed in 7.15).

Source: cve.now feed data

Am I affected, and how do I check?

The advisory covers WP Database Backup plugin version 7.14 and earlier. The installed version is shown on the WordPress Plugins screen, and it can be compared against that 7.14 cutoff.

Source: patchstack.com

How do I fix CVE-2026-129065?

Upgrade the WP Database Backup plugin to version 7.15, which is the listed fixed version.

Source: patchstack.com

No corrections so far. Something wrong on this page? Report an error.