Pagelayer <= 2.0.9 - Incorrect Authorization to Authenticated (Contributor+) Mail Relay Configuration via 'contacts'
Strategic Overview
- Status
- Patched in 2.1.0
- Affected Plugin
- Page Builder: Pagelayer – Drag and Drop website builder
- Affected Version
<= 2.0.9- CVSS
- 4.3Medium
- Weakness type
- CWE-863 · Incorrect Authorization
- CVE
CVE-2026-2470
At a glance
CVE-2026-2470 is a medium-severity Incorrect Authorization vulnerability in the Page Builder: Pagelayer WordPress plugin, affecting versions <= 2.0.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.1.0; sites on affected versions should update now. Disclosed June 2026, reported by Drew Webber (mcdruid).
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-863: Incorrect Authorization
Reaching this weakness in Page Builder: Pagelayer <= 2.0.9 takes an account at Contributor level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.
The action runs for users the code intended to exclude, with the same effect as having no check at all. For Page Builder: Pagelayer the fix is 2.1.0: builds <= 2.0.9 are affected, anything from 2.1.0 onward is not.
Remediation
Update to version 2.1.0, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Page Builder: Pagelayer 2.1.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Page Builder: Pagelayer – Drag and Drop website builder
- 8.8CVE-2020-35944: Page Builder: Pagelayer CSRF to Cross-Site Scripting
CVE-2020-35944 - 7.4CVE-2020-35947: Page Builder: Pagelayer XSS
CVE-2020-35947 - 7.2CVE-2023-4687: Page Builder: Pagelayer Stored XSS
CVE-2023-4687 - 6.4CVE-2026-3297: Page Builder: Pagelayer Stored XSS
CVE-2026-3297 - 6.4CVE-2026-2509: Page Builder: Pagelayer <= 2.0.8 Stored XSS
CVE-2026-2509 - 6.4CVE-2024-13427: Page Builder: Pagelayer Stored XSS
CVE-2024-13427 - 6.4CVE-2025-24573: PageLayer <= 1.9.4 Stored Cross-Site Scripting
CVE-2025-24573 - 6.4CVE-2024-2504: Page Builder: Pagelayer Stored XSS
CVE-2024-2504
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C