CVE-2020-13643

Page Builder by SiteOrigin <= 2.10.15 - Cross-Site Request Forgery to Reflected Cross-Site Scripting

2020-05-11 00:00
Chloe Chamberland

Strategic Overview

Status
Patched in 2.10.16
Affected Plugin
Page Builder by SiteOrigin
Affected Version
< 2.10.16
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2020-13643
View all Page Builder by SiteOrigin vulnerabilities

At a glance

CVE-2020-13643 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Page Builder by SiteOrigin WordPress plugin, affecting versions < 2.10.16. 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 2.10.16; sites on affected versions should update now. Disclosed May 2020, reported by Chloe Chamberland.

Vulnerability Overview

An issue was discovered in the SiteOrigin Page Builder plugin before 2.10.16 for WordPress. The live editor feature did not do any nonce verification, allowing for requests to be forged on behalf of an administrator. The live_editor_panels_data $_POST variable allows for malicious JavaScript to be executed in the victim's browser.

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 by SiteOrigin < 2.10.16 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 by SiteOrigin the fix is 2.10.16: builds < 2.10.16 are affected, anything from 2.10.16 onward is not.

Remediation

Update to version 2.10.16, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2020-13643https://www.wordfence.com/threat-intel/vulnerabilities/id/28e1a11b-5320-41be-bc78-580322e5f407https://nvd.nist.gov/vuln/detail/CVE-2020-13643

Related records

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