CVE-2025-1926

Page Builder: Pagelayer – Drag and Drop website builder <= 1.9.8 - Cross-Site Request Forgery (CSRF) To Post Contents Modification

2025-03-09 16:20
Brian Sans-Souci (liardom)

Strategic Overview

Status
Patched in 1.9.9
Affected Plugin
Page Builder: Pagelayer – Drag and Drop website builder
Affected Version
<= 1.9.8
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-1926
View all Page Builder: Pagelayer – Drag and Drop website builder vulnerabilities

At a glance

CVE-2025-1926 is a medium-severity Cross-Site Request Forgery (CSRF) 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 no authentication. The issue is fixed in version 1.9.9; 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 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.

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 privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Page Builder: Pagelayer <= 1.9.8 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Page Builder: Pagelayer the fix is 1.9.9: builds <= 1.9.8 are affected, anything from 1.9.9 onward is not.

Remediation

Update to version 1.9.9, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Page Builder: Pagelayer: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Page Builder: Pagelayer 1.9.9 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-1926https://www.wordfence.com/threat-intel/vulnerabilities/id/542b6312-b264-49d5-882a-454427c60c8ahttps://nvd.nist.gov/vuln/detail/CVE-2025-1926

Related records

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