Vulnerability · CVE-2023-3388
beautiful-cookie-banner beautiful_cookie_consent_banner Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Published Feb 1, 2023 · corrected/updated Feb 1, 2023 · beautiful-cookie-banner beautiful_cookie_consent_banner · evidence confidence very high
The Beautiful Cookie Consent Banner for WordPress is vulnerable to Stored Cross-Site Scripting via the 'nsc_bar_content_href' parameter in versions up to, and including, 2.10.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. A partial patch was made available in 2.10.1 and the issue was fully patched in 2.10.2.
Grounded briefings
Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.
Executive
CVE-2023-3388 is a unknown public vulnerability record for beautiful-cookie-banner beautiful_cookie_consent_banner. CISA lists it as known exploited. Published remediation guidance: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.
System administrator
Identify whether beautiful-cookie-banner beautiful_cookie_consent_banner is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: beautiful-cookie-banner beautiful_cookie_consent_banner. Published remediation guidance: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.
Security analyst
Signals on file: no CVSS/EPSS yet. CISA lists it as known exploited. Sources contributing to this record: cve_org, vulncheck_kev. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.
Exploitation and remediation
Exploitation evidence
Confirmed in CISA KEV since Feb 1, 2023. Listed in CISA KEV and VulnCheck KEV.
Patch and remediation
Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Safe detection guidance
Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Feb 1, 2023 · VulnCheck KEV
Detected
The Beautiful Cookie Consent Banner for WordPress is vulnerable to Stored Cross-Site Scripting via the 'nsc_bar_content_href' parameter in versions up to, and including, 2.10.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. A partia
Feb 1, 2023 · CISA KEV
Known exploited
Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Affected
- vendor beautiful-cookie-banner beautiful_cookie_consent_bannerversion unspecified
Sources
- CVE.orgVulnerability recordCVE-2023-3388
Official CVE identifier
cve.org - VulnCheck KEVConfirmed exploitationCVE-2023-3388
The Beautiful Cookie Consent Banner for WordPress is vulnerable to Stored Cross-Site Scripting via the 'nsc_bar_content_href' parameter in versions up to, and including, 2.10.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated
vulncheck.com