CVE-2023-3409

Bricks <= 1.8.1 - Cross-Site Request Forgery via reset_settings

2024-08-16 00:00
Ram

Strategic Overview

Status
Patched in 1.8.2
Affected Theme
Bricks
Affected Version
<= 1.8.1
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-3409
View all Bricks vulnerabilities

At a glance

CVE-2023-3409 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Bricks WordPress theme, affecting versions <= 1.8.1. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.8.2; sites on affected versions should update now. Disclosed August 2024, reported by Ram.

Vulnerability Overview

The Bricks theme for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.8.1. This is due to missing or incorrect nonce validation on the 'reset_settings' function. This makes it possible for unauthenticated attackers to reset the theme's settings 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)

Bricks <= 1.8.1 carries this weakness at reset_settings, 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 Bricks the fix is 1.8.2: builds <= 1.8.1 are affected, anything from 1.8.2 onward is not.

Remediation

Update to version 1.8.2, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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