Plugins · pagelayer · data as of 2026-11-01
Is Page Builder safe? Known vulnerabilities and latest version
- Latest version
- 2.2.2
- Last updated
- 2026-09-24
- Active installs
- 400,000+
- Known issues on record
- 19
- Unpatched in latest
- 0
- Tested up to WP
- 7.0.8 · PHP 5.5+
The most advanced frontend drag & drop page builder. Pagelayer is a light weight but extremely powerful Website Builder. — by Softaculous
What to do
- Update to the latest version (2.2.2). Anything older than 2.1.0 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get pagelayer --field=version shows what you run; wp plugin update pagelayer updates it.
Check your version
Known vulnerabilities
19 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 4.3 CVE-2026-2470 · published 2026-06-13
Missing authorization check in Page Builder (2.0.9 and older)
- Affected
- 2.0.9 and older
- Fixed in
- 2.1.0 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Incorrect Authorization in all versions up to, and including, 2.0.9. This is due to the pagelayer_save_content AJAX handler allowing users with basic post-edit capability to persist pagelayer_contact_templates metadata on posts they can edit (including pending posts), while the unauthenticated pagelayer_contact_submit endpoint later consumes that metadata by user-controlled post/form identifiers without enforcing a privileged or published-context boundary. This makes it possible for authenticated attackers, with Contributor-level access and above, to configure arbitrary contact-form mail templates that are usable through unauthenticated form submission via the contacts parameter. In typical deployments this template feature is configured via Pagelayer Pro UI; however, the vulnerable backend trust path is still present. This issue may be chained with CVE-2026-2442 to increase exploitability and attacker control over outbound email behavior.
medium 6.4 CVE-2026-3297 · published 2026-06-13
Stored cross-site scripting (XSS) in Page Builder (2.0.9 and older)
- Affected
- 2.0.9 and older
- Fixed in
- 2.1.0 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Anchor block in versions up to, and including, 2.0.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
medium 6.4 CVE-2026-2509 · published 2026-04-08
Stored cross-site scripting (XSS) in Page Builder (2.0.8 and older)
- Affected
- 2.0.8 and older
- Fixed in
- 2.0.9 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Page Builder: Pagelayer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Button widget's Custom Attributes field in all versions up to, and including, 2.0.8. This is due to an incomplete event handler blocklist in the 'pagelayer_xss_content' XSS filtering function, which blocks common, but not all, event handlers. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
NVD CVE-2026-2509Wordfence advisoryCode change (fix)Plugin source
medium 4.3 CVE-2026-39469 · published 2026-04-08
Information disclosure in Page Builder (2.0.8 and older)
- Affected
- 2.0.8 and older
- Fixed in
- 2.0.9
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Softaculous PageLayer pagelayer allows Retrieve Embedded Sensitive Data.This issue affects PageLayer: from n/a through <= 2.0.8.
medium 5.3 CVE-2026-2442 · published 2026-03-28
Security issue in Page Builder (2.0.7 and older)
- Affected
- 2.0.7 and older
- Fixed in
- 2.0.8 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Improper Neutralization of CRLF Sequences ('CRLF Injection') in all versions up to, and including, 2.0.7. This is due to the contact form handler performing placeholder substitution on attacker-controlled form fields and then passing the resulting values into email headers without removing CR/LF characters. This makes it possible for unauthenticated attackers to inject arbitrary email headers (for example Bcc / Cc) and abuse form email delivery via the 'email' parameter granted they can target a contact form configured to use placeholders in mail template headers.
medium 4.3 CVE-2025-12366 · published 2025-11-13
Missing authorization check in Page Builder (2.0.5 and older)
- Affected
- 2.0.5 and older
- Fixed in
- 2.0.6 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.0.5 via the pagelayer_replace_page function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Author-level access and above, to replace media files belonging to other users, including administrators.
NVD CVE-2025-12366Wordfence advisoryCode change (fix)Plugin source
medium 4.7 CVE-2025-4223 · published 2025-05-24
Reflected cross-site scripting (XSS) in Page Builder (2.0.0 and older)
- Affected
- 2.0.0 and older
- Fixed in
- 2.0.1 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘login_url’ parameter in all versions up to, and including, 2.0.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. A valid username/password pair needs to be supplied in order to be successfully exploited and any injected scripts will only execute in the context of that authenticated user.
NVD CVE-2025-4223Wordfence advisoryCode change (fix)Plugin source
medium 6.4 CVE-2024-13427 · published 2025-05-24
Stored cross-site scripting (XSS) in Page Builder (2.0.0 and older)
- Affected
- 2.0.0 and older
- Fixed in
- 2.0.1 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Button widget in all versions up to, and including, 2.0.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. NOTE: This vulnerability was partially fixed in version 1.9.9 and completely fixed in version 2.0.1.
medium 4.3 CVE-2025-2104 · published 2025-03-13
Missing authorization check in Page Builder (1.9.8 and older)
- Affected
- 1.9.8 and older
- Fixed in
- 1.9.9 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to unauthorized post publication due to insufficient validation on the pagelayer_save_content() function in all versions up to, and including, 1.9.8. This makes it possible for authenticated attackers, with Contributor-level access and above, to bypass post moderation and publish posts to the site.
medium 4.3 CVE-2024-13430 · published 2025-03-12
Information disclosure in Page Builder (1.9.8 and older)
- Affected
- 1.9.8 and older
- Fixed in
- 1.9.9 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.9.8 via the 'pagelayer_builder_posts_shortcode' function due to insufficient restrictions on which posts can be included. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract data from private posts that they should not have access to.
medium 4.3 CVE-2025-1926 · published 2025-03-10
Cross-site request forgery (CSRF) in Page Builder (1.9.8 and older)
- Affected
- 1.9.8 and older
- Fixed in
- 1.9.9 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.9.8. This is due to missing or incorrect nonce validation on the pagelayer_save_post function. This makes it possible for unauthenticated attackers to modify post contents via a forged request, granted they can trick a site administrator into performing an action such as clicking on a link.
medium 6.5 CVE-2025-24573 · published 2025-01-24
Cross-site scripting (XSS) in Page Builder (1.9.4 and older)
- Affected
- 1.9.4 and older
- Fixed in
- 1.9.5
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Softaculous PageLayer pagelayer allows DOM-Based XSS.This issue affects PageLayer: from n/a through <= 1.9.4.
medium 4.3 CVE-2023-49196 · published 2024-12-09
Missing authorization check in Page Builder (1.7.7 and older)
- Affected
- 1.7.7 and older
- Fixed in
- 1.7.8
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in Pagelayer Team PageLayer allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects PageLayer: from n/a through 1.7.7.
medium 4.8 CVE-2024-43972 · published 2024-09-18
Stored cross-site scripting (XSS) in Page Builder (1.8.7 and older)
- Affected
- 1.8.7 and older
- Fixed in
- 1.8.8
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Pagelayer Team PageLayer allows Stored XSS.This issue affects PageLayer: from n/a through 1.8.7.
high 8.8 CVE-2024-30465 · published 2024-06-09
Missing authorization check in Page Builder (1.8.1 and older)
- Affected
- 1.8.1 and older
- Fixed in
- 1.8.2
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Missing Authorization vulnerability in Pagelayer Team PageLayer.This issue affects PageLayer: from n/a through 1.8.1.
medium 5.4 CVE-2024-2504 · published 2024-04-09
Stored cross-site scripting (XSS) in Page Builder (1.8.4 and older)
- Affected
- 1.8.4 and older
- Fixed in
- 1.8.5 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'attr' parameter in all versions up to, and including, 1.8.4 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
NVD CVE-2024-2504Wordfence advisoryCode change (fix)Plugin source
medium 5.4 CVE-2024-2127 · published 2024-03-07
Stored cross-site scripting (XSS) in Page Builder (1.8.3 and older)
- Affected
- 1.8.3 and older
- Fixed in
- 1.8.4 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via custom attributes in all versions up to, and including, 1.8.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
medium 5.4 CVE-2024-1590 · published 2024-02-23
Stored cross-site scripting (XSS) in Page Builder (1.8.2 and older)
- Affected
- 1.8.2 and older
- Fixed in
- 1.8.3 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Button Widget in all versions up to, and including, 1.8.2 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
medium 5.4 CVE-2023-6738 · published 2024-01-04
Stored cross-site scripting (XSS) in Page Builder (1.7.8 and older)
- Affected
- 1.7.8 and older
- Fixed in
- 1.7.9 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'pagelayer_header_code', 'pagelayer_body_open_code', and 'pagelayer_footer_code' meta fields in all versions up to, and including, 1.7.8 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This appears to be a reintroduction of a vulnerability patched in version 1.7.7.
NVD CVE-2023-6738Wordfence advisoryCode change (fix)Plugin source
Recent activity
- 2026-09-24 — latest release on wordpress.org (2.2.2).
- 2026-06-13 — Missing authorization check disclosed (CVE-2026-2470), fixed in 2.1.0.
- 2026-06-13 — Stored cross-site scripting (XSS) disclosed (CVE-2026-3297), fixed in 2.1.0.
- 2026-04-08 — Stored cross-site scripting (XSS) disclosed (CVE-2026-2509), fixed in 2.0.9.
Get an email when Page Builder has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Page Builder (pagelayer) is published or a fix ships. Unsubscribe in one click.
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/pagelayer (Plugins API), fetched 2026-11-01.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-01. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/pagelayer"><img src="https://laskyr.com/plugins/pagelayer/badge.svg" alt="Page Builder vulnerability status"></a>