CVE-2025-12366

Page Builder: Pagelayer – Drag and Drop website builder <= 2.0.5 - Authenticated (Author+) Insecure Direct Object Reference

2025-11-12 15:20
Athiwat Tiprasaharn (Jitlada)

Strategic Overview

Status
Patched in 2.0.6
Affected Plugin
Page Builder: Pagelayer – Drag and Drop website builder
Affected Version
<= 2.0.5
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2025-12366
View all Page Builder: Pagelayer – Drag and Drop website builder vulnerabilities

At a glance

CVE-2025-12366 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Page Builder: Pagelayer WordPress plugin, affecting versions <= 2.0.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 2.0.6; sites on affected versions should update now. Disclosed November 2025, reported by Athiwat Tiprasaharn (Jitlada).

Vulnerability Overview

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.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Page Builder: Pagelayer <= 2.0.5 takes an account at Author level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Page Builder: Pagelayer the fix is 2.0.6: builds <= 2.0.5 are affected, anything from 2.0.6 onward is not.

Remediation

Update to version 2.0.6, 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.6 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-12366https://www.wordfence.com/threat-intel/vulnerabilities/id/2216d82c-29ae-4355-8118-6ebc49726c12https://nvd.nist.gov/vuln/detail/CVE-2025-12366

Related records

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