CVE-2024-1361

Colibri Page Builder <= 1.0.253 - Cross-Site Request Fogery via extend_builder

2024-02-22 00:00
Lucio Sá

Strategic Overview

Status
Patched in 1.0.260
Affected Plugin
Colibri Page Builder
Affected Version
<= 1.0.253
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-1361
View all Colibri Page Builder vulnerabilities

At a glance

CVE-2024-1361 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Colibri Page Builder WordPress plugin, affecting versions <= 1.0.253. 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.0.260; sites on affected versions should update now. Disclosed February 2024, reported by Lucio Sá.

Vulnerability Overview

The Colibri Page Builder plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.253. This is due to missing or incorrect nonce validation on the apiCall() function. This makes it possible for unauthenticated attackers to call a limited set of functions that can be used to import images, delete posts, or save theme data 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)

Colibri Page Builder <= 1.0.253 carries this weakness at apiCall(), and reaching it 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 Colibri Page Builder the fix is 1.0.260: builds <= 1.0.253 are affected, anything from 1.0.260 onward is not.

Remediation

Update to version 1.0.260, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Colibri Page Builder: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Colibri Page Builder 1.0.260 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