WordPress Core <= 7.1 - Authenticated (Author+) Missing Authorization to Comment/Note Reparenting via REST API

2026-09-17 00:00
viridis

Strategic Overview

Status
Patched in 6.6.8
Affected Core
WordPress 7.1
Affected Version
6.6.7 – 7.1 · 6 branches
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all WordPress 7.1 vulnerabilities

At a glance

This record tracks a medium-severity Missing Authorization vulnerability in the WordPress 7.1 WordPress release line, affecting 6.6.7 – 7.1 · 6 branches. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 6.6.8; sites on affected versions should update now. Disclosed September 2026, reported by viridis.

Vulnerability Overview

WordPress Core is vulnerable to Missing Authorization via the REST comments controller update_item_permissions_check() in various versions up to, and including, 7.1 because the target post is not authorized when a comment or note's parent post is changed - only the current parent was checked. This makes it possible for an authenticated attacker who can edit a comment (e.g. an Author editing a comment on their own post) to reparent it onto an arbitrary post, including posts they can neither read nor edit.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

WordPress 7.1 6.6.7 – 7.1 · 6 branches carries this weakness at update_item_permissions_check(), and reaching it takes an account at Author level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WordPress 7.1 the fix is 6.6.8: builds 6.6.7 – 7.1 · 6 branches are affected, anything from 6.6.8 onward is not.

Remediation

Update to one of the following versions, or a newer patched version: 6.6.8, 6.7.8, 6.8.9, 6.9.8, 7.0.5, 7.1.1

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: updating to 6.6.8 is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/8b8d4431-ac72-45a2-b4a1-19690946d0ee

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C