WordPress component: A security weakness
WordPress component is affected by a security weakness. Exploitation requires an authenticated subscriber account. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- WordPress component
- Plugin slug
Core- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Mar 11, 2026
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Mar 11, 2026 and is one of 47 known issues for WordPress core.
Update, patch or deactivate.
No fixed release is identified. Update WordPress component when a confirmed fixed release becomes available; until then, disable and remove it when the site's risk warrants.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N