CVE-2025-12505 json
weDocs <= 2.1.14 - Missing Authorization to Settings Update
published 11mo ago modified 27d ago also EUVD-2025-201513
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2025-12505 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 11mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
Affected products
- wedevs weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot
Classification
- Weakness
-
- CWE-285 Improper Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/3ec54ec6-0ff1-4290-85d0-d691a1832627?source=cve
- github.com /weDevsOfficial/wedocs-plugin/blob/develop/includes/API/SettingsApi.php
- plugins.trac.wordpress.org /browser/wedocs/tags/2.1.13/includes/API/SettingsApi.php#L115
- plugins.trac.wordpress.org /browser/wedocs/tags/2.1.13/includes/API/SettingsApi.php#L179
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&new=3403375%40wedocs%2Ftrunk&old=3382516%40wedocs%2Ftrunk&sfp_email
Sources
- CVE List CVE-2025-12505
- NVD CVE-2025-12505
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.