dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-10579

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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 BackWPup – WordPress Backup & Restore Plugin plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'backwpup_working' AJAX action in all versions up to, and including, 5.5.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve access to a back-up's filename while a backup is running. This information has little value on it's own, but could be used to aid in a brute force attack to retrieve back-up contents in limited environments (i.e. NGINX).

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 BackWPup WordPress plugin lacks a capability check on the 'backwpup_working' AJAX action, allowing any authenticated user with Subscriber-level privileges or higher to query backup filenames while a backup is running. This is a broken access control (CWE-862) vulnerability exposing limited metadata that could theoretically aid in brute force attempts against backup files in restricted server environments.

MitigationUpdate to version 5.5.1 or later which should include the missing capability check. If no update is available, restrict the 'backwpup_working' AJAX action to users with higher privileges using a WordPress capability check or firewall rule.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Identify BackWPup plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for the backwpup folder, or look for BackWPup in the WordPress admin plugins list. View the main plugin file (usually backwpup.php) to read the Version header.
    Affected if BackWPup plugin is installed and the installed version is lower than 5.5.1
  2. Confirm low-privilege user existence
    Check WordPress user database (wp_usermeta table, wp_capabilities key) for users with the 'subscriber' role. In WordPress admin, go to Users > All Users to list roles.
    Affected if Any user account with Subscriber-level role exists on the site
  3. Verify AJAX endpoint accessibility
    Send a POST request to /wp-admin/admin-ajax.php with action=backwpup_working while authenticated as a low-privilege user (Subscriber). Use a tool like curl with valid user credentials.
    Affected if The request returns a successful response (HTTP 200) without requiring higher privileges, indicating the AJAX action is accessible to subscribers
  4. Check for backup filename exposure
    Analyze the response from the backwpup_working AJAX action. Look for any metadata containing backup job names, filenames, or paths that should not be visible to low-privilege users.
    Affected if The AJAX response contains backup filenames, job identifiers, or file paths accessible to subscriber-level users

A user is affected if BackWPup version is below 5.5.1, the site has any Subscriber-level users, and the backwpup_working AJAX action returns backup metadata without proper capability validation.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 5.5.1 or later which should include the missing capability check. If no update is available, restrict the 'backwpup_working' AJAX action to users with higher privileges using a WordPress capability check or firewall rule.

Recommended fix Moderate confidence

BackWPup 5.5.1 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the BackWPup plugin
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, you can update by going to Dashboard > Updates and selecting BackWPup to update
  6. After updating, verify the version number reflects the patched release

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10579 — 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-2025-10579 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