GCVE - cpe:2.3:a:themeum:wp_page_builder:*:*:*:*:*:wordpress:*:*

Approved changes feed: RSS · Atom

cpe:2.3:a:themeum:wp_page_builder:*:*:*:*:*:wordpress:*:*

part: a version: * update: *

Vendor	Themeum (`12449a9f-b8a3-5f81-9e39-f958a6d45415`)
Product	Wp Page Builder (`5ef93175-0109-5567-81c7-d5995b691cc8`)
Edition	*
Language	*
Software edition	*
Target software	wordpress
Target hardware	*
Other	*
Notes	Imported from gcve-enriched-dumps CVE data

PURL mappings

PURL	Source	Last updated
No PURL mappings for this CPE yet.

Vulnerability references

Identifier	cpeApplicability	Submitted	db.gcve.eu details	Rationale
`CVE:CVE-2022-40963`	vulnerable	2026-06-03 14:48:03.742298	WordPress WP Page Builder plugin <= 1.2.6 - Multiple Auth. Stored Cross-Site Scripting (XSS) vulnerabilities MEDIUM (4.8) Multiple Auth. (author+) Stored Cross-Site Scripting (XSS) vulnerabilities in WP Page Builder plugin <= 1.2.6 on WordPress. Published: 2022-11-18T22:19:45.378Z Updated: 2026-04-28T16:07:49.256Z Open on db.gcve.eu Reference links https://patchstack.com/database/vulnerability/wp-pagebuilder/wordpress-wp-page-builder-plugin-1-2-6-multiple-auth-stored-cross-site-scripting-xss-vulnerabilities?_s_id=cve https://wordpress.org/plugins/wp-pagebuilder/	Imported from gcve-enriched-dumps CVE data
`CVE:CVE-2022-3830`	vulnerable	2026-06-03 14:47:59.361131	WP Page Builder <= 1.2.8 - Admin+ Stored Cross-Site 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). Published: 2022-12-05T16:50:33.163Z Updated: 2025-04-24T13:22:41.136Z Open on db.gcve.eu Reference links https://wpscan.com/vulnerability/98b2321d-fb66-4e02-9906-63af7b08d647	Imported from gcve-enriched-dumps CVE data
`CVE:CVE-2021-24208`	vulnerable	2026-06-03 14:43:56.459402	WP Page Builder < 1.2.4 - Multiple Stored Cross-Site scripting (XSS) The editor of the WP Page Builder WordPress plugin before 1.2.4 allows lower-privileged users to insert unfiltered HTML, including JavaScript, into pages via the “Raw HTML” widget and the “Custom HTML” widgets (though the custom HTML widget requires sending a crafted request - it appears that this widget uses some form of client side validation but not server side validation), all of which are added via the “page_builder_data” parameter when performing the “wppb_page_save” AJAX action. It is also possible to insert malicious JavaScript via the “wppb_page_css” parameter (this can be done by closing out the style tag and opening a script tag) when performing the “wppb_page_save” AJAX action. Published: 2021-04-05T18:27:46.000Z Updated: 2024-08-03T19:21:18.776Z Open on db.gcve.eu Reference links https://www.themeum.com/wp-page-builder-updated-v1-2-4/ https://wpscan.com/vulnerability/c20e243d-b0de-4ae5-9a0d-b9d02c9b8141	Imported from gcve-enriched-dumps CVE data
`CVE:CVE-2021-24207`	vulnerable	2026-06-03 14:43:56.458937	WP Page Builder < 1.2.4 - Insecure default configuration Allows Subscribers Editing Access to Posts By default, the WP Page Builder WordPress plugin before 1.2.4 allows subscriber-level users to edit and make changes to any and all posts pages - user roles must be specifically blocked from editing posts and pages. Published: 2021-04-05T18:27:46.000Z Updated: 2024-08-03T19:21:18.845Z Open on db.gcve.eu Reference links https://wpscan.com/vulnerability/21e7a46f-e9a3-4b20-b44a-a5b6ce7b7ce6 https://www.themeum.com/wp-page-builder-updated-v1-2-4/	Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.