WordPress weDocs plugin <= 2.6.1 - Broken Access Control vulnerability
- Exploited
- No known exploitation
- Fix
- Fixed in 2.6.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.6.2.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 28/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
The WordPress weDocs plugin, a documentation tool for WordPress sites, has a broken access control flaw that lets an attacker read information they should not be able to see. The flaw can be reached remotely, without logging in, and the attacker needs no action from a user.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Missing Authorization vulnerability in weDevs weDocs wedocs allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects weDocs: from n/a through 2.6.1.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.6.2.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- wedocs
through 2.6.1
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121760
Is CVE-2026-121760 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The plugin fails to properly check who is allowed to use some of its pages or actions. A user can therefore reach pages or perform actions they should not be permitted to, such as viewing other people's data.Source: patchstack.com
Which versions are affected by CVE-2026-121760?
wedocs: through 2.6.1.Source: cve.now feed data
Am I affected, and how do I check?
All weDocs plugin versions up to and including 2.6.1 are affected. To check, open the plugin list in the WordPress admin and read the version shown next to weDocs.Source: patchstack.com
How do I fix CVE-2026-121760?
Update the weDocs plugin to version 2.6.2 or later, as the vendor's fix is in that release.Source: patchstack.com