Page Builder · Security record

Is Page Builder safe?

No known vulnerability affects the current version (2.2.2). 34 issues were found in earlier versions and fixed, the latest disclosed on Jun 12, 2026.

Checked 4 days ago against the WPVulnerability database, for version 2.2.2.

How it’s looked after

Last release: Sep 24, 2026 (1 month ago)
Releases in the last year: 17
Tested up to: WordPress 7.0.8
Support resolved: 0 of 1 threads in two months
Active installs: 400K+

34 known vulnerabilities

2 high
25 medium
7 not rated

None affects the current version.

Disclosed each year

20205
20236
20249
20257
20265

Every known vulnerability in Page Builder

Newest first, with any that affect the current version at the top.

medium
Incorrect Authorization to Authenticated (Contributor+) Mail Relay Configuration via 'contacts'
Fixed in 2.1.0 · CVE-2026-2470 · Jun 12, 2026 · Wordfence
medium
Authenticated (Contributor+) Stored Cross-Site Scripting via Anchor Block
Fixed in 2.1.0 · CVE-2026-3297 · Jun 12, 2026 · Wordfence
Authenticated (Contributor+) Stored Cross-Site Scripting via Button Widget Custom Attributes
Fixed in 2.0.9 · CVE-2026-2509 · Apr 7, 2026 · Wordfence
Improper Neutralization of CRLF Sequences to Unauthenticated Email Header Injection via 'email'
Fixed in 2.0.8 · CVE-2026-2442 · Mar 27, 2026 · Wordfence
medium
Authenticated (Contributor+) Information Exposure
Fixed in 2.0.9 · CVE-2026-39469 · Mar 12, 2026 · Wordfence
medium
Authenticated (Author+) Insecure Direct Object Reference
Fixed in 2.0.6 · CVE-2025-12366 · Nov 12, 2025 · Wordfence
medium
Reflected Cross-Site Scripting via login_url Parameter
Fixed in 2.0.1 · CVE-2025-4223 · May 23, 2025 · Wordfence
medium
Authenticated (Contributor+) Stored Cross-Site Scripting via Button Link
Fixed in 2.0.1 · CVE-2024-13427 · May 23, 2025 · Wordfence
medium
Missing Authorization to Authenticated (Contributor+) Post Publication
Fixed in 2.0.0 · CVE-2025-2104 · Mar 12, 2025 · Wordfence
medium
Authenticated (Contributor+) Private Post Disclosure in pagelayer_builder_posts_shortcode
Fixed in 1.9.9 · CVE-2024-13430 · Mar 11, 2025 · Wordfence
medium
Cross-Site Request Forgery (CSRF) To Post Contents Modification
Fixed in 1.9.9 · CVE-2025-1926 · Mar 9, 2025 · Wordfence
medium
Authenticated (Contributor+) Stored Cross-Site Scripting
Fixed in 1.9.5 · CVE-2025-24573 · Jan 24, 2025 · Wordfence
medium
Authenticated (Admin+) Stored Cross-Site Scripting
Fixed in 1.9.0 · CVE-2024-8618 · Sep 4, 2024 · Wordfence
medium
Authenticated (Administrator+) Stored Cross-Site Scripting
Fixed in 1.8.8 · CVE-2024-43972 · Aug 28, 2024 · Wordfence
medium
Authenticated (Admin+) Stored Cross-Site Scripting
Fixed in 1.8.8 · CVE-2024-8426 · Jul 28, 2024 · Wordfence
medium
Missing Authorization
Fixed in 1.8.2 · CVE-2024-30465 · Mar 28, 2024 · Wordfence
medium
Authenticated(Contributor+) Stored Cross-Site Scripting via custom attributes
Fixed in 1.8.5 · CVE-2024-2504 · Mar 21, 2024 · Wordfence
medium
Authenticated (Contributor+) Stored Cross-Site Scripting via Custom Attributes
Fixed in 1.8.4 · CVE-2024-2127 · Mar 7, 2024 · Wordfence
medium
Authenticated (Contributor+) Stored Cross-Site Scripting via Button
Fixed in 1.8.3 · CVE-2024-1590 · Feb 22, 2024 · Wordfence
medium
Authenticated(Administrator+) Stored Cross-Site Scripting via Header/Footer code
Fixed in 1.8.0 · CVE-2023-5124 · Jan 29, 2024 · Wordfence
medium
Authenticated(Contributor+) Stored Cross-Site Scripting via meta fields
Fixed in 1.7.9 · CVE-2023-6738 · Jan 3, 2024 · Wordfence
medium
Authenticated (Admin+) Stored Cross-Site Scripting
Fixed in 1.8.1 · CVE-2023-7115 · Dec 24, 2023 · Wordfence
medium
Cross-Site Request Forgery via pagelayer_load_plugin
Fixed in 1.7.8 · CVE-2023-49196 · Dec 1, 2023 · Wordfence
medium
Authenticated (Author+) Stored Cross-Site Scripting via Header/Footer
Fixed in 1.7.8 · CVE-2023-5087 · Sep 25, 2023 · Wordfence
medium
Missing Authorization to Stored Cross-Site Scripting
Fixed in 1.7.7 · CVE-2023-4687 · Sep 25, 2023 · Wordfence
WordPress PageLayer Plugin < 1.7.7 is vulnerable to Cross Site Scripting (XSS)
Fixed in 1.7.7 · Sep 14, 2023 · Patchstack
Authenticated (Contributor+) Stored Cross-Site Scripting
Fixed in 1.7.7 · Sep 13, 2023 · Wordfence
Reflected Cross-Site Scripting (XSS) vulnerability
Fixed in 1.3.5 · Dec 10, 2020 · Patchstack
medium
Reflected Cross-Site Scripting via Color Settings
Fixed in 1.3.5 · CVE-2020-36384 · Dec 10, 2020 · Wordfence
medium
Reflected Cross-Site Scripting via font-size
Fixed in 1.3.5 · CVE-2020-36383 · Dec 10, 2020 · Wordfence
high
Missing Authorization to Cross-Site Scripting
Fixed in 1.1.2 · CVE-2020-35947 · May 28, 2020 · Wordfence
high
Cross-Site Request Forgery to Cross-Site Scripting
Fixed in 1.1.2 · CVE-2020-35944 · May 28, 2020 · Wordfence
Authenticated (Contributor+) Stored Cross-Site Scripting
Fixed in 1.7.7 · WPScan
Multiple Reflected Cross-Site Scripting (XSS)
Fixed in 1.3.5 · WPScan

Questions about Page Builder’s security

Is Page Builder safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Page Builder updated: most attacks target sites that haven’t updated.

Does Page Builder have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 34 older issues, fixed in earlier versions, so keep Page Builder up to date.

Is Page Builder still maintained?

Yes. Its last release was 1 month ago. Its authors resolved 0 of the 1 support threads opened in the last two months.

Is Page Builder compatible with the latest WordPress?

It’s tested up to WordPress 7.0.8, one version behind the current 7.1. Authors often update this line a few weeks after a release.

Hear about the next one first

Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.

Start free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.