CVE-2026-39520: weDevs weDocs missing authorization in access control levels

CVE-2026-39520 · Severity: medium · CVSS 5.3 · Published 2026-04-08

weDocs is a WordPress plugin used to create and manage documentation for products or services. A security flaw in the plugin's access control settings allows unauthorized individuals to bypass intended security levels. This could lead to the exposure of restricted documentation or information that was meant to be private or limited to specific user roles.

Technologies: weDevs weDocs. Vendors: weDevs.

Quick answers

Is CVE-2026-39520 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-39520 being exploited in the wild.
How severe is CVE-2026-39520?
Medium severity, with a CVSS score of 5.3, published 8 April 2026.
Which products and versions are affected?
weDevs weDocs <= 2.1.18.
Is there a fix for CVE-2026-39520?
A patch was published on 2026-02-25: Version 2.2.1 released to address the issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-39520 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-39520?
Check whether you run weDevs weDocs at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The weDocs plugin for WordPress is vulnerable to a missing authorization (CWE-862) flaw in versions up to and including 2.1.18. The vulnerability stems from a failure to properly validate user permissions when accessing components governed by security level configurations. An unauthenticated remote attacker can exploit this to bypass intended access restrictions and view or interact with restricted documentation content. The issue is resolved in version 2.2.1, which introduces proper authorization checks.

Affected products

  • weDevs weDocs <= 2.1.18

Timeline

  • 2026-01-26: other: Vulnerability reported by researcher hhhai
  • 2026-02-25: disclosed: Initial disclosure by Patchstack
  • 2026-04-08: advisory: CVE-2026-39520 published
  • 2026-02-25: patched: Version 2.2.1 released to address the issue

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.