CVE-2022-3830 WP Page Builder <= 1.2.8 - Admin+ Stored Cross-Site
Admin users can inject malicious scripts into WP Page Builder settings, enabling stored XSS attacks in multisite environments.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2022-3830?
CVE-2022-3830 is a medium-severity cross-site scripting vulnerability in Unknown WP Page Builder, published on 5 Dec 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Official description
The WP Page Builder WordPress plugin through 1.2.8 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).
Which versions are affected by CVE-2022-3830?
It affects 1 product.
Products include Themeum Wp Page Builder.
How do I fix CVE-2022-3830?
No fix has been published for CVE-2022-3830 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2022-3830 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3830 exists.
Other vulnerabilities in Unknown WP Page Builder
- CVE-2021-24208 WP Page Builder < 1.2.4 - Multiple Stored Cross-Site scripting (XSS)
- CVE-2022-40963 WordPress WP Page Builder plugin <= 1.2.6 - Multiple Auth. Stored Cross-Site Scripting (XSS) vulnerabilities
- CVE-2021-24207 WP Page Builder < 1.2.4 - Insecure default configuration Allows Subscribers Editing Access to Posts
Sources
Also known as GHSA-w6hf-m4jf-9v6x.