Woostify Sites Library <= 1.4.7 - Missing Authorization to Authenticated (Subscriber+) Limited Options Update
Strategic Overview
- Status
- Patched in 1.4.8
- Affected Plugin
- Woostify Sites Library
- Affected Version
<= 1.4.7- CVSS
- 8.1High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-6279
At a glance
CVE-2023-6279 is a high-severity Missing Authorization vulnerability in the Woostify Sites Library WordPress plugin, affecting versions <= 1.4.7. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.4.8; sites on affected versions should update now. Disclosed January 2024, reported by Krzysztof Zając.
Vulnerability Overview
The Woostify Sites Library plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on several AJAX actions like 'woostify_sites_child_theme' in all versions up to, and including, 1.4.7. This makes it possible for authenticated attackers, with subscriber-level access and above, to update arbitrary options to 'activated' which can lead to a denial of service.
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 integrity, availability.
CWE-862: Missing Authorization
Woostify Sites Library <= 1.4.7 carries this weakness at woostify_sites_child_theme, 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 Woostify Sites Library the fix is 1.4.8: builds <= 1.4.7 are affected, anything from 1.4.8 onward is not.
Remediation
Update to version 1.4.8, 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: Woostify Sites Library 1.4.8 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Woostify Sites Library
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C