CVE-2020-35944

Page Builder: Pagelayer – Drag and Drop website builder <= 1.1.1 - Cross-Site Request Forgery to Cross-Site Scripting

2020-05-28 00:00
Chloe Chamberland

Strategic Overview

Status
Patched in 1.1.2
Affected Version
< 1.1.2
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2020-35944
View all Page Builder: Pagelayer – Drag and Drop website builder vulnerabilities

At a glance

CVE-2020-35944 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Page Builder: Pagelayer WordPress plugin, affecting versions < 1.1.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.1.2; sites on affected versions should update now. Disclosed May 2020, reported by Chloe Chamberland.

Vulnerability Overview

An issue was discovered in the PageLayer plugin before 1.1.2 for WordPress. The pagelayer_settings_page function is vulnerable to CSRF, which can lead to XSS.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

Reaching this weakness in Page Builder: Pagelayer < 1.1.2 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.1.2: builds < 1.1.2 are affected, anything from 1.1.2 onward is not.

Remediation

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

  • Firewall
  • Alerts

External References

Related records

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