Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-3906

WordPress core is vulnerable to unauthorized access in versions 6.9 th ...

Overview

Published
11 Mar 2026
Modified
17 Jun 2026
Medium CVE
2 Registry packages
2 OS packages
2 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

4.3 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Weakness: CWE-862

Affected packages · 2

Packages affected by CVE-2026-3906
EcosystemPackageVulnerableFixed in
Bitnami wordpress >=6.9.0, <6.9.2 6.9.2
Bitnami wordpress-multisite >=6.9.0, <6.9.2 6.9.2

Open a package to see all its vulnerabilities.

Operating systems · 2 fixes

debian 1 release · 1 package

fixed 1
wordpress
debian fixes for CVE-2026-3906
ReleasePackageFixed in
14 wordpress 6.9.4+dfsg1-1

minimos 1 release · 1 package

fixed 1
wordpress-6
minimos fixes for CVE-2026-3906
ReleasePackageFixed in
wordpress-6 6.9.2-r0

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.