dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-10176

HIGH · 7.2 CVSS v3.1 Published 2025-09-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 The Hack Repair Guy's Plugin Archiver plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the prepare_items function in all versions up to, and including, 2.0.4. This makes it possible for authenticated attackers, with Administrator-level access and above, 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 Hack Repair Guy's Plugin Archiver WordPress plugin (versions up to 2.0.4) contains an arbitrary file deletion vulnerability in the prepare_items function due to insufficient file path validation. Authenticated administrators can supply arbitrary file paths and cause their deletion, enabling deletion of critical files like wp-config.php for RCE escalation.

MitigationUpdate the plugin to version 2.0.5 or later which contains proper path validation. If patching is not possible immediately, deactivate and remove the plugin until the update can be applied.

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify if the Plugin Archiver plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'plugin-archiver' or containing 'archiver' related to Hack Repair Guy. Alternatively, query the WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins';
    Affected if The plugin folder exists in wp-content/plugins/ and the plugin is listed in active_plugins.
  2. Determine the installed plugin version
    Locate the plugin's main PHP file (usually plugin-archiver.php) and read the plugin header comment which contains the Version field. Alternatively, check the readme.txt file in the plugin directory for the 'Stable tag' entry.
    Affected if The version read from the plugin header or readme.txt is 2.0.4 or lower.
  3. Verify the vulnerable prepare_items function exists
    Open the plugin's main PHP file and search for the function named 'prepare_items'. This function is reported to contain the arbitrary file deletion vulnerability due to insufficient path validation.
    Affected if The prepare_items function exists in the plugin code, indicating the vulnerable code is present.
  4. Confirm administrator-level access exists
    Review WordPress user roles: in the WordPress admin dashboard, go to Users > All Users and check for accounts with 'Administrator' role. Alternatively, query: SELECT * FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%administrator%';
    Affected if There is at least one user account with Administrator role who can access the WordPress admin panel.
  5. Check for recent unauthorized file deletions
    Review WordPress audit logs, server access logs, or file system modification timestamps. Look for deletions of critical files (wp-config.php, .htaccess, index.php) that occurred without administrator action. Check: ls -la wp-config.php and compare modification time to known admin activities.
    Affected if Critical WordPress files have been deleted or modified without authorized administrator action, or audit logs show unusual deletion requests to the plugin's archiver functionality.

A user is affected if the Hack Repair Guy's Plugin Archiver plugin versions 2.0.4 or lower is installed and active, allowing any administrator account to trigger arbitrary file deletion through the prepare_items function.

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 plugin to version 2.0.5 or later which contains proper path validation. If patching is not possible immediately, deactivate and remove the plugin until the update can be applied.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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