XStore <= 9.3.8 - Authenticated (Subscriber+) Arbitrary Options Update
Strategic Overview
- Status
- Patched in 9.3.9
- Affected Theme
- XStore
- Affected Version
<= 9.3.8- CVSS
- 8.8High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-33564
At a glance
CVE-2024-33564 is a high-severity Missing Authorization vulnerability in the XStore WordPress theme, affecting versions <= 9.3.8. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 9.3.9; sites on affected versions should update now. Disclosed April 2024, reported by Rafie Muhammad.
Vulnerability Overview
The XStore theme for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on a function in all versions up to, and including, 9.3.8. This makes it possible for authenticated attackers, with subscriber-level access and above, to update arbitrary options which can be used to achieve privilege escalation.
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 confidentiality, integrity, availability — full site compromise territory.
CWE-862: Missing Authorization
Reaching this weakness in XStore <= 9.3.8 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 XStore the fix is 9.3.9: builds <= 9.3.8 are affected, anything from 9.3.9 onward is not.
Remediation
Update to version 9.3.9, 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: XStore 9.3.9 closes this, and updating the theme is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in XStore
- 10.0CVE-2024-33559: XStore <= 9.3.8 SQL Injection
CVE-2024-33559 - 9.8CVE-2024-33560: XStore <= 9.3.8 Local File Inclusion
CVE-2024-33560 - 8.8CVE-2025-11746: XStore | Multipurpose WooCommerce Theme <= 9.5.4 LFI
CVE-2025-11746 - 7.5CVE-2026-3326: XStore < 9.7.3 SQL Injection
CVE-2026-3326 - 7.5CVE-2025-64193: XStore < 9.6.1 Local File Inclusion
CVE-2025-64193 - 6.5CVE-2026-25006: XStore <= 9.6.4 Arbitrary Shortcode Execution
CVE-2026-25006 - 6.5CVE-2025-60100: XStore < 9.6 Arbitrary Shortcode Execution
CVE-2025-60100 - 6.4CVE-2026-25305: XStore <= 9.6.4 Stored Cross-Site Scripting
CVE-2026-25305
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C