CVE-2025-12505
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 weDocs plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 2.1.14. This is due to the plugin not properly verifying that a user is authorized to perform an action in the create_item_permissions_check function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify global plugin settings.
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 weDocs WordPress plugin fails to properly enforce authorization in its create_item_permissions_check function, allowing authenticated users with only Subscriber-level privileges to modify global plugin settings that should be restricted to administrators.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm weDocs plugin is installedNavigate to WordPress Admin > Plugins and verify weDocs appears in the installed plugins list, or check for the presence of /wp-content/plugins/wedocs/ directoryAffected if weDocs plugin is installed and active
-
Verify the installed versionIn WordPress Admin > Plugins, click on weDocs and view the version number displayed, or read the main plugin PHP file header for the Version constantAffected if Installed version is lower than 2.1.15 or the version cannot be determined
-
Test subscriber-level access to plugin settingsLog in as a user with the Subscriber role and attempt to access the weDocs settings endpoint (typically /wp-admin/admin.php?page=wedocs-settings or the REST API endpoint for settings), or intercept a settings save request with a subscriber-level authentication tokenAffected if A user with only Subscriber privileges can access or successfully modify global plugin settings without receiving a permission denied error
-
Inspect the create_item_permissions_check functionLocate and review the create_item_permissions_check function in the weDocs plugin REST API handler file (commonly in includes/classes/class-rest.php or similar), and verify whether it checks for administrator-level capabilities such as manage_options before allowing settings modificationsAffected if The function allows settings modification requests to proceed without verifying the user has administrator-level capabilities
You are affected if weDocs is installed with a version below 2.1.15 and users with only Subscriber role can modify global plugin settings that should be restricted to administrators.
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 weDocs plugin to version 2.1.15 or later which contains the patch, or implement custom access control at the application level to enforce proper capability checks for global settings modifications.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12505 — 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-12505 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