Skip to main content

CVE-2026-3906: WordPress Core Auth Bypass Vulnerability

CVE-2026-3906 is an authentication bypass flaw in WordPress 6.9 through 6.9.1 that allows Subscriber-level users to create notes on any post. This article covers technical details, affected versions, and mitigation steps.

Updated:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-3906 Overview

CVE-2026-3906 is a missing authorization vulnerability in WordPress core versions 6.9 through 6.9.1. The flaw resides in the Notes feature, a block-level collaboration annotation system introduced in WordPress 6.9 for editorial comments within the block editor. The REST API create_item_permissions_check() method in the comments controller fails to verify edit_post permission on the target post when creating a note. Authenticated attackers holding Subscriber-level access can create notes on any post, including content authored by other users, private posts, and posts in any status. The issue is tracked under CWE-862 (Missing Authorization).

Critical Impact

Subscriber-level users can inject editorial annotations onto any post in the site, violating content authorship boundaries and exposing private posts to unauthorized modification of associated metadata.

Affected Products

  • WordPress Core 6.9
  • WordPress Core 6.9.1
  • Sites using the Notes (block-level collaboration annotations) feature

Discovery Timeline

  • 2026-03-11 - CVE-2026-3906 published to NVD
  • 2026-04-22 - Last updated in NVD database

Technical Details for CVE-2026-3906

Vulnerability Analysis

The Notes feature in WordPress 6.9 extends the comments subsystem to support block-level editorial annotations. Notes are created through the WordPress REST API, which routes write operations through the WP_REST_Comments_Controller class. Permission enforcement for comment creation lives in create_item_permissions_check() at line 562 of class-wp-rest-comments-controller.php. The method validates that the requester can create comments in general but does not call current_user_can( 'edit_post', $post_id ) against the target post identifier supplied in the request. As a result, any authenticated account, including the minimum Subscriber role, can submit a note targeting any post ID.

The flaw affects integrity rather than confidentiality. Attackers cannot read post contents through this endpoint, but they can attach notes to drafts, private posts, scheduled posts, and posts owned by administrators or editors.

Root Cause

The root cause is a missing authorization check ([CWE-862]) in the REST permission callback. The controller treats note creation as equivalent to a generic comment write operation, omitting the per-post capability check required when the target object is editorial content. Authentication is verified, but authorization against the specific resource is not.

Attack Vector

Exploitation requires network access to the WordPress REST API and any authenticated session with Subscriber privileges or higher. The attacker issues a POST request to the comments endpoint, specifying the target post ID and the note payload. No user interaction is required and complexity is low. Because Subscriber registration is open on many WordPress deployments, the privilege threshold is effectively minimal.

The vulnerability is described in prose because no public proof-of-concept code is available. Technical details of the flawed permission callback are visible in the WordPress REST API source and the fix in WordPress Changeset #61888.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-3906

Indicators of Compromise

  • Notes attached to posts where the note author lacks edit_post capability on the target post.
  • REST API POST requests to /wp-json/wp/v2/comments originating from Subscriber-level accounts and referencing post IDs in private, draft, or future status.
  • Unexpected entries in the wp_comments table tagged as notes against posts owned by administrators or editors.

Detection Strategies

  • Audit WordPress database tables for note-type comment records and correlate the user_id of the note author with the post_author of the referenced post.
  • Review web server access logs for POST requests to the comments REST endpoint sent by low-privilege user sessions.
  • Deploy a WordPress security plugin that flags REST API calls failing post-level capability checks.

Monitoring Recommendations

  • Enable verbose REST API request logging and forward records to a centralized analytics platform for retrospective review.
  • Alert on Subscriber accounts issuing write operations against the comments endpoint outside of normal user behavior baselines.
  • Track creation of new Subscriber accounts followed shortly by REST API write activity, which can indicate automated probing.

How to Mitigate CVE-2026-3906

Immediate Actions Required

  • Upgrade WordPress core to a patched release beyond 6.9.1 that incorporates Changeset #61888.
  • Audit existing notes created since deploying 6.9 to identify entries authored by users without edit_post rights on the parent post.
  • Disable open user registration if it is not required for site functionality.

Patch Information

The WordPress core team addressed the flaw in Changeset #61888 by adding an edit_post capability check inside create_item_permissions_check() for note creation. Administrators should apply the corresponding WordPress 6.9.x maintenance release. Additional context is available in the Wordfence Vulnerability Report.

Workarounds

  • Restrict access to the /wp-json/wp/v2/comments REST endpoint at the web server or WAF layer for unauthenticated and Subscriber-level sessions until the patch is deployed.
  • Temporarily disable the Notes feature via a custom plugin or must-use plugin that unregisters the note comment type.
  • Set users_can_register to false in WordPress settings to reduce the attacker pool while patching is scheduled.
bash
# Configuration example: disable open registration via WP-CLI
wp option update users_can_register 0

# Verify installed WordPress version before and after upgrade
wp core version
wp core update

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.