Beautiful Cookie Consent Banner <= 2.10.0 - Missing Authorization to Settings Update
Strategic Overview
- Status
- Patched in 2.10.1
- Affected Plugin
- Beautiful Cookie Consent Banner
- Affected Version
<= 2.10.0- CVSS
- 7.3High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a high-severity Missing Authorization vulnerability in the Beautiful Cookie Consent Banner WordPress plugin, affecting versions <= 2.10.0. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.10.1; sites on affected versions should update now. Disclosed January 2023.
Vulnerability Overview
The Beautiful Cookie Consent Banner plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the nsc_bar_save_submitted_form_fields() function called via and admin_init hook in versions up to, and including, 2.10.0. This makes it possible for unauthenticated attackers to modify the plugin's settings and inject malicious web scripts. Please note this is still vulnerable to Cross-Site Request Forgery attacks.
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 privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Beautiful Cookie Consent Banner <= 2.10.0 carries this weakness at nsc_bar_save_submitted_form_fields(), and reaching it 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 Beautiful Cookie Consent Banner the fix is 2.10.1: builds <= 2.10.0 are affected, anything from 2.10.1 onward is not.
Remediation
Update to version 2.10.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: Beautiful Cookie Consent Banner 2.10.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Beautiful Cookie Consent Banner
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C