Apus Framework <= 2.4 - Authenticated (Subscriber+) Arbitrary Options Update in import_page_options
Strategic Overview
- Status
- Patched in 2.5
- Affected Plugin
- Apus Framework
- Affected Version
<= 2.4- CVSS
- 8.8High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-12296
At a glance
CVE-2024-12296 is a high-severity Missing Authorization vulnerability in the Apus Framework WordPress plugin, affecting versions <= 2.4. 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 2.5; sites on affected versions should update now. Disclosed February 2025, reported by Tonn.
Vulnerability Overview
The Apus Framework plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the 'import_page_options' function in all versions up to, and including, 2.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site. NOTE: This vulnerability was partially fixed in version 2.4.
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
Apus Framework <= 2.4 carries this weakness at import_page_options, 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 Apus Framework the fix is 2.5: builds <= 2.4 are affected, anything from 2.5 onward is not.
Remediation
Update to version 2.5, 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: Apus Framework 2.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C