CVE-2022-3823 json
Beautiful Cookie Consent Banner < 2.9.1 - Admin+ Stored XSS
published 3y ago modified 4mo ago also EUVD-2022-43164
- cvss
- 4.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
The Beautiful Cookie Consent Banner WordPress plugin before 2.9.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).
Patch / fix
- Unknown Beautiful Cookie Consent Banner 2.9.1
Is CVE-2022-3823 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/a072b091-5e5f-4e88-bd3d-2f4582e6564e referenced PoC, tagged "exploit" by a source, unverified
- wpscan.com https://wpscan.com/vulnerability/a072b091-5e5f-4e88-bd3d-2f4582e6564e/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N |
| CNA | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N |
Affected products
- Unknown Beautiful Cookie Consent Banner
Classification
- Technology feeds
References
-
wpscan.com
/vulnerability/a072b091-5e5f-4e88-bd3d-2f4582e6564e
exploit, technical-description, third-party-advisory
-
wpscan.com
/vulnerability/a072b091-5e5f-4e88-bd3d-2f4582e6564e/
exploit
Sources
- CVE List CVE-2022-3823
- NVD CVE-2022-3823
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.