dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-4030

HIGH · 8.1 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Database Backup for WordPress plugin for WordPress is vulnerable to unauthorized arbitrary file read and deletion 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 combined with a user-controlled backup directory parameter. This makes it possible for unauthenticated attackers to read and delete arbitrary files on the server, leading to Sensitive Information Exposure and potential site takeover. Note: This vulnerability is only exploitable in WordPress Multisite environments where the deprecated is_site_admin() function exists.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Database Backup for WordPress plugin fails to properly enforce authorization check return values while allowing a user-controlled backup directory parameter, enabling unauthenticated attackers on WordPress Multisite installations to read and delete arbitrary files via the deprecated is_site_admin() function.

MitigationUpdate to a patched version when available; until then, disable the plugin on Multisite installations or restrict unauthorized access to prevent unauthenticated file operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WordPress Multisite installation
    Check if the constant MULTISITE is defined as true in wp-config.php, or query the wp_options table for option_name='active_sitewide_plugins' or check wp_blogs table for multiple blogs
    Affected if WordPress is running as a Multisite network (this is required for the vulnerability to be exploitable)
  2. Verify Database Backup plugin is installed
    Check the wp-content/plugins directory for a folder named 'database-backup' or similar, or query wp_options for option_name='active_plugins' containing 'database-backup'
    Affected if The Database Backup for WordPress plugin files exist in the plugins directory
  3. Confirm plugin is network-activated on Multisite
    Query wp_sitemeta table for option_name='active_sitewide_plugins' containing the plugin slug, or check Network Admin > Plugins screen for network-wide activation status
    Affected if The plugin is network-activated (network-wide activation makes it exploitable by any site admin across the network)
  4. Check installed plugin version
    Read the plugin main file header in wp-content/plugins/[plugin-folder]/[plugin-file].php to find the 'Version:' comment, or query wp_options for the plugin version option
    Affected if The installed version matches or falls within the affected unpatched version range (no specific version provided, so compare to any available patched version)
  5. Verify backup directory parameter is accessible
    Check if the plugin's backup functionality is exposed via an AJAX action or admin URL that accepts a 'backup_dir' or 'backup_directory' parameter, or test accessing the backup endpoint without authentication
    Affected if The backup feature accepts user-controlled directory parameters without proper authorization validation

A user is affected if they run WordPress Multisite with the Database Backup plugin network-activated or active on a subsite, and the plugin version is unpatched, allowing unauthenticated file read/delete operations via the vulnerable backup directory parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version when available; until then, disable the plugin on Multisite installations or restrict unauthorized access to prevent unauthenticated file operations.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4030 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4030 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data