CVE-2025-12505

weDocs <= 2.1.14 - Missing Authorization to Settings Update

Strategic Overview

Status
Patched in 2.1.15
Affected Version
<= 2.1.14
CVSS
5.4Medium
Weakness type
CWE-285 · Improper Authorization
CVE
CVE-2025-12505
View all weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot vulnerabilities

At a glance

CVE-2025-12505 is a medium-severity Improper Authorization vulnerability in the weDocs WordPress plugin, affecting versions <= 2.1.14. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.1.15; sites on affected versions should update now. Disclosed December 2025, reported by Md. Moniruzzaman Prodhan (NomanProdhan).

Vulnerability Overview

The 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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-285: Improper Authorization

Reaching this weakness in weDocs <= 2.1.14 takes a caller who can reach the endpoint. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.

A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For weDocs the fix is 2.1.15: builds <= 2.1.14 are affected, anything from 2.1.15 onward is not.

Remediation

Update to version 2.1.15, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: weDocs 2.1.15 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C