VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

Beautiful Cookie Consent Banner <= 2.10.0 — Missing Authorization to Settings Update

aee6fea2-dbf6-4155-ba3f-f85ea3520504Published · Updated

Action summary

Affected: ≤2.10.0Update to 2.10.1 or newer

All remediation steps
Watch plugin
Severity
High7.3
CVSS
7.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:L Confidentiality
Low
I:L Integrity
Low
A:L Availability
Low
Weakness
CWE-862 Missing Authorization
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

Beautiful Cookie Consent Banner beautiful-and-responsive-cookie-consent

  1. Affected≤ 2.10.0
  2. Patched in2.10.1

Update to 2.10.1 or newer.

You are affected if you run ≤ 2.10.0. Version 2.10.1 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Beautiful Cookie Consent Banner.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 2.10.1, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Beautiful Cookie Consent Banner to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Beautiful Cookie Consent Banner

All 4
More vulnerabilities in Beautiful Cookie Consent Banner
SeverityVulnerabilityCVEPublished
Medium6.1Reflected Cross-Site Scripting
≤4.6.1Update to 4.6.2
CVE-2025-49866
High7.2Unauthenticated Stored Cross-Site Scripting
≤2.10.1Update to 2.10.2
CVE-2023-3388
Medium5.5Authenticated (Admin+) Stored Cross-Site Scripting
≤2.9.0Update to 2.9.1
CVE-2022-3823

Same weakness (Missing Authorization)

All Missing Authorization
Other Missing Authorization vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent Header
EZ SQL Reports Shortcode Widget and DB Backup≤5.25.25Update to 5.26.45
CVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form Submission
Chatterbug Forms – Fast, Flexible WordPress Form Builder≤1.0.2Update to 1.1
CVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' Parameter
ELEX WordPress HelpDesk & Customer Ticketing System≤3.3.9Update to 3.4.0
CVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity high, CVSS 7.3

  2. Record last updated

Sources & licenses

Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?