CVE-2025-10188
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 · uneditedThe The Hack Repair Guy's Plugin Archiver plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.4. This is due to missing or incorrect nonce validation on the bulk_remove() function. This makes it possible for unauthenticated attackers to arbitrary directory deletion in /wp-content via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 confidenceThe Hack Repair Guy's Plugin Archiver WordPress plugin lacks proper nonce validation on the bulk_remove() function in all versions up to 2.0.4. This CSRF vulnerability allows unauthenticated attackers to delete arbitrary directories within /wp-content by tricking an authenticated administrator into clicking a malicious link, leading to potential site disruption or data loss.
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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the Plugin Archiver plugin is installedNavigate to WordPress admin > Plugins and look for 'Plugin Archiver' or 'Hack Repair Guy\'s Plugin Archiver', or check the /wp-content/plugins/ directory for a folder containing 'archiver' in the nameAffected if The plugin is present in the plugins directory
-
Identify the installed version numberIn WordPress admin, click on the plugin name to view details, or open the main plugin PHP file and look for the 'Version:' header in the plugin comment blockAffected if The version is 2.0.4 or lower (including any 2.0.x, 1.x.x, or unversioned releases)
-
Verify the plugin is activeCheck the Plugins page in WordPress admin - the plugin must be activated for the vulnerability to be exploitableAffected if The Plugin Archiver plugin shows as 'Active'
-
Check for the bulk_remove function accessibilityLocate the plugin PHP files and search for the 'bulk_remove' function definition. Verify if it performs a nonce check (look for wp_verify_nonce or check_admin_referer) before executing directory deletion logicAffected if The bulk_remove function exists and lacks nonce validation on the delete operation
You are affected if Plugin Archiver is installed, active, and version 2.0.4 or below, with the bulk_remove function present without proper nonce protection.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to the latest version when available, or disable and remove the plugin until a patch is released. If the plugin must remain in use, implement additional CSRF protections and monitor for suspicious admin actions.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10188 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10188 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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