Freemius SDK <= 2.2.3 - Missing Authorization to Arbitrary Options Update
Strategic Overview
- Status
- Patched in 3.2.6.1
- Affected Version
< 3.2.6.1- CVSS
- 8.8High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a high-severity Missing Authorization vulnerability in the BuddyPress WooCommerce My Account Integration. Create WooCommerce Member Pages WordPress plugin, affecting versions < 3.2.6.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.2.6.1; sites on affected versions should update now. Disclosed February 2019.
Vulnerability Overview
The Freemius SDK for WordPress is vulnerable to authorization bypass due to a missing capability check on the _get_db_option and _set_db_option functions in versions up to, and including, 2.2.3. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to change site settings and potentially take over 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-862: Missing Authorization
Reaching this weakness in BuddyPress WooCommerce My Account Integration. Create WooCommerce Member Pages < 3.2.6.1 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 BuddyPress WooCommerce My Account Integration. Create WooCommerce Member Pages the fix is 3.2.6.1: builds < 3.2.6.1 are affected, anything from 3.2.6.1 onward is not.
Remediation
Update to version 3.2.6.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: BuddyPress WooCommerce My Account Integration. Create WooCommerce Member Pages 3.2.6.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 6.3CVE-2022-4974: Freemius SDK <= 2.4.2 Missing Authorization Checks
CVE-2022-4974 - 4.3CVE-2024-13358: BuddyPress WooCommerce My… Authenticated
CVE-2024-13358 - 4.3CVE-2025-1780: BuddyPress WooCommerce My Account… CSRF
CVE-2025-1780 - 4.3CVE-2024-35726: BuddyPress WooCommerce My… Missing Authorization
CVE-2024-35726
Other vulnerabilities in BuddyPress WooCommerce My Account Integration. Create WooCommerce Member Pages
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C