CVE-2025-9331

Spacious <= 1.9.11 - Missing Authorization to Autheticated (Subscriber+) Demo Data Import

2025-08-21 22:13
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 1.9.12
Affected Theme
Spacious
Affected Version
<= 1.9.11
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-9331
View all Spacious vulnerabilities

At a glance

CVE-2025-9331 is a medium-severity Missing Authorization vulnerability in the Spacious WordPress theme, affecting versions <= 1.9.11. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.9.12; sites on affected versions should update now. Disclosed August 2025, reported by Dmitrii Ignatyev.

Vulnerability Overview

The Spacious theme for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'welcome_notice_import_handler' function in all versions up to, and including, 1.9.11. This makes it possible for authenticated attackers, with Subscriber-level access and above, to import demo data into the site.

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

Spacious <= 1.9.11 carries this weakness at welcome_notice_import_handler, and reaching it takes a caller who can reach the endpoint. 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 Spacious the fix is 1.9.12: builds <= 1.9.11 are affected, anything from 1.9.12 onward is not.

Remediation

Update to version 1.9.12, or a newer patched version

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: Spacious 1.9.12 closes this, and updating the theme is the step that ends it.

  • Login Security
  • Alerts

External References

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