WordPress Core <= 7.0.2 - Authenticated (Subscriber+) Missing Authorization to Arbitrary Site Creation on Multisite

2026-08-08 00:00
Aikido Security

Strategic Overview

Status
Patched in 4.7.34
Affected Core
WordPress 7.0
Affected Version
4.7.0 – 7.0.2 · 24 branches
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all WordPress 7.0 vulnerabilities

At a glance

This record tracks a medium-severity Missing Authorization vulnerability in the WordPress 7.0 WordPress release line, affecting 4.7.0 – 7.0.2 · 24 branches. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.7.34; sites on affected versions should update now. Disclosed August 2026, reported by Aikido Security.

Vulnerability Overview

WordPress Core is vulnerable to unauthorized site creation due to a missing check on the active signup policy in the 'gimmeanotherblog' signup action in all versions up to, and including, 7.0.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create new sites on a multisite network that has been configured to allow user registration but not site registration. This issue only affects multisite installations.

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.0 4.7.0 – 7.0.2 · 24 branches carries this weakness at gimmeanotherblog, and reaching it takes an account at Subscriber 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.0 the fix is 4.7.34: builds 4.7.0 – 7.0.2 · 24 branches are affected, anything from 4.7.34 onward is not.

Remediation

Update to one of the following versions, or a newer patched version: 4.7.34, 4.8.29, 4.9.30, 5.0.26, 5.1.23, 5.2.25, 5.3.22, 5.4.20, 5.5.19, 5.6.18, 5.7.16, 5.8.14, 5.9.14, 6.0.13, 6.1.11, 6.2.10, 6.3.9, 6.4.9, 6.5.9, 6.6.6, 6.7.6, 6.8.7, 6.9.6, 7.0.3

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 4.7.34 is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/80f92f7f-72e7-4d83-9ceb-ed0e11fb8003

Related records

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