iubenda <= 3.3.2 - Authenticated (Subscriber+) Privilege Escalation
Strategic Overview
- Status
- Patched in 3.3.3
- Affected Version
<= 3.3.2- CVSS
- 8.8High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2022-3911
At a glance
CVE-2022-3911 is a high-severity Missing Authorization vulnerability in the iubenda WordPress plugin, affecting versions <= 3.3.2. 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 3.3.3; sites on affected versions should update now. Disclosed December 2022, reported by Krzysztof Zając.
Vulnerability Overview
The ubenda plugin for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 3.3.2. This is due to missing verification in the 'process_actions' and 'ajax_save_options' functions (among numerous others). This makes it possible for subscriber-level attackers to perform ajax actions (such as updating plugin options) that are normally only available to higher-level authenticated users. This can include granting new privileges to ones own account.
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
iubenda <= 3.3.2 carries this weakness at process_actions, 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 iubenda the fix is 3.3.3: builds <= 3.3.2 are affected, anything from 3.3.3 onward is not.
Remediation
Update to version 3.3.3, 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: iubenda 3.3.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in iubenda | All-in-one Compliance for GDPR / CCPA Cookie Consent + more
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C