WP-Stateless – Google Cloud Storage <= 3.4.0 - Missing Authorization to Limited Arbitrary Options Update
Strategic Overview
- Status
- Patched in 3.4.1
- Affected Plugin
- WP-Stateless – Google Cloud Storage
- Affected Version
<= 3.4.0- CVSS
- 7.1High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-1385
At a glance
CVE-2024-1385 is a high-severity Missing Authorization vulnerability in the WP-Stateless WordPress plugin, affecting versions <= 3.4.0. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity; high availability impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.4.1; sites on affected versions should update now. Disclosed April 2024, reported by Krzysztof Zając.
Vulnerability Overview
The WP-Stateless – Google Cloud Storage plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the dismiss_notices() function in all versions up to, and including, 3.4.0. This makes it possible for authenticated attackers, with subscriber-level access and above, to update arbitrary option values to the current time, which may completely take a site offline.
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. A successful exploit has high impact on availability.
CWE-862: Missing Authorization
WP-Stateless <= 3.4.0 carries this weakness at dismiss_notices(), 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 WP-Stateless the fix is 3.4.1: builds <= 3.4.0 are affected, anything from 3.4.1 onward is not.
Remediation
Update to version 3.4.1, 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: WP-Stateless 3.4.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP-Stateless – Google Cloud Storage
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C