CVE-2025-10754
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 DocoDoco Store Locator plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the zip upload functionality in all versions up to, and including, 1.0.1. This makes it possible for authenticated attackers, with Editor-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.
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 DocoDoco Store Locator WordPress plugin (versions up to 1.0.1) lacks proper file type validation in its zip upload functionality, allowing authenticated users with Editor-level permissions or higher to upload arbitrary files including malicious PHP scripts that could lead to remote code execution.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm DocoDoco Store Locator plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'docodoco-store-locator' or similar, or query the wp_options table for the option 'active_plugins'Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in the active plugins list
-
Identify the installed plugin versionOpen the main plugin file (usually docodoco-store-locator.php) and locate the version string in the plugin header comment (e.g., 'Version: 1.0.1')Affected if The reported version is 1.0.1 or any version prior to a patched release
-
Determine if zip upload functionality existsSearch the plugin files for functions handling file uploads, particularly .zip file processing. Look for 'zip', 'upload', 'wp_handle_upload', or similar terms in the plugin codeAffected if The plugin contains code that handles zip file uploads for store data import or similar features
-
Verify Editor-level or higher user accounts existQuery the wp_usermeta table for users with wp_capabilities containing 'editor', 'author', 'administrator', or 'shop_manager' rolesAffected if There are one or more users with Editor-level permissions or higher who can access the plugin upload feature
-
Check if the upload endpoint is accessible to EditorsExamine the plugin code for capability checks (using current_user_can or similar) on upload-related functions. A vulnerable plugin will allow Editor-level access to the upload functionalityAffected if The upload function lacks proper capability checks or allows users with 'edit_posts' capability to upload files
You are affected if the DocoDoco Store Locator plugin is installed at version 1.0.1 or earlier, contains zip upload functionality, and allows Editor-level users to access that upload feature without proper file type validation.
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 to a patched version of the plugin once available; in the interim, disable the zip upload functionality or restrict Editor-level user capabilities to prevent exploitation.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10754 — 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-10754 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