CVE-2025-2104

Page Builder: Pagelayer – Drag and Drop website builder <= 1.9.9 - Missing Authorization to Authenticated (Contributor+) Post Publication

2025-03-12 00:00
Brian Sans-Souci (liardom)

Strategic Overview

Status
Patched in 2.0.0
Affected Plugin
Page Builder: Pagelayer – Drag and Drop website builder
Affected Version
<= 1.9.8
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-2104
View all Page Builder: Pagelayer – Drag and Drop website builder vulnerabilities

At a glance

CVE-2025-2104 is a medium-severity Missing Authorization vulnerability in the Page Builder: Pagelayer WordPress plugin, affecting versions <= 1.9.8. 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.0.0; sites on affected versions should update now. Disclosed March 2025, reported by Brian Sans-Souci (liardom).

Vulnerability Overview

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.

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-862: Missing Authorization

Page Builder: Pagelayer <= 1.9.8 carries this weakness at pagelayer_save_content(), and reaching it takes an account at Contributor level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Page Builder: Pagelayer the fix is 2.0.0: builds <= 1.9.8 are affected, anything from 2.0.0 onward is not.

Remediation

Update to version 2.0.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.0.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-2104https://www.wordfence.com/threat-intel/vulnerabilities/id/2e3897fb-0f40-4111-8a7d-60415e1f9f96https://nvd.nist.gov/vuln/detail/CVE-2025-2104

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C