WordPress up to 6.9.1 Notes Feature create_item_permissions_check authorization

Summaryinfo

A vulnerability was found in WordPress up to 6.9.1. It has been declared as problematic. This impacts the function create_item_permissions_check of the component Notes Feature. The manipulation results in authorization. This vulnerability is known as CVE-2026-3906. It is possible to launch the attack remotely. No exploit is available.

Detailsinfo

A vulnerability classified as problematic has been found in WordPress up to 6.9.1. Affected is the function create_item_permissions_check of the component Notes Feature. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on integrity. CVE summarizes:

WordPress core is vulnerable to unauthorized access in versions 6.9 through 6.9.1. The Notes feature (block-level collaboration annotations) was introduced in WordPress 6.9 to allow editorial comments directly on posts in the block editor. However, the REST API `create_item_permissions_check()` method in the comments controller did not verify that the authenticated user has `edit_post` permission on the target post when creating a note. This makes it possible for authenticated attackers with Subscriber-level access to create notes on any post, including posts authored by other users, private posts, and posts in any status.

The weakness was published by kaminuma. The advisory is available at wordfence.com. This vulnerability is traded as CVE-2026-3906 since 03/10/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 03/19/2026).

The vulnerability scanner Nessus provides a plugin with the ID 302884 (Linux Distros Unpatched Vulnerability : CVE-2026-3906), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Tenable (302884) and CERT Bund (WID-SEC-2026-0684). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

• Open Source WordPress

Productinfo

Type

• Content Management System

Name

• WordPress

Version

• 6.9.0
• 6.9.1

License

• open-source

Website

• Product: https://wordpress.com/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion