dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-7712

CRITICAL · 9.1 CVSS v3.1 Published 2025-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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 Madara - Core plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the wp_manga_delete_zip() function in all versions up to, and including, 2.2.3. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

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 Madara - Core WordPress plugin contains an unauthenticated arbitrary file deletion vulnerability in the wp_manga_delete_zip() function due to insufficient path validation. Attackers can exploit this to delete any file on the server by manipulating file paths, potentially achieving RCE by deleting wp-config.php or other critical files.

MitigationUpdate the Madara - Core plugin to the latest version when available. Until then, consider disabling the plugin or deploying a WAF rule to block requests to the vulnerable function.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Verify Madara - Core plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Madara - Core' or 'Madara' in the list, or check the /wp-content/plugins/ directory for a folder containing 'madara' in the name
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    In WordPress admin > Plugins, click on the Madara - Core plugin to view its version number, or open the main plugin PHP file (usually in wp-content/plugins/madara-core/ or similar) and look for a 'Version:' header in the plugin comments
    Affected if The installed version is older than the latest patched version (when available)
  3. Confirm vulnerable function exists
    Examine the plugin files in wp-content/plugins/ for a file containing 'wp_manga_delete_zip' function - search the codebase using grep or a file search tool for this function name
    Affected if The function wp_manga_delete_zip() is found in the plugin code
  4. Check if vulnerable endpoint is exposed
    Test access to the WordPress AJAX endpoint (wp-admin/admin-ajax.php) with a crafted request to trigger the delete function - examine the plugin's JavaScript or AJAX handlers to identify the action name used (often 'manga_delete_zip' or similar)
    Affected if The AJAX endpoint responds to requests without authentication for the vulnerable action
  5. Look for signs of file deletion exploitation
    Check if wp-config.php or other critical WordPress files have been recently deleted or modified, and review server access logs for requests to admin-ajax.php with parameters related to zip or file deletion
    Affected if Critical files are missing or access logs show suspicious file deletion requests

A user is affected if the Madara - Core plugin is installed and the installed version is vulnerable to arbitrary file deletion via the wp_manga_delete_zip function, with the vulnerable endpoint exposed without authentication.

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 the Madara - Core plugin to the latest version when available. Until then, consider disabling the plugin or deploying a WAF rule to block requests to the vulnerable function.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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