CVE-2024-1504

SecuPress Free — WordPress Security <= 2.2.5.1 - Cross-Site Request Forgery to Banned IP Address

2024-04-01 00:00
Lucio Sá

Strategic Overview

Status
Patched in 2.2.5.2
Affected Plugin
SecuPress with Simple SSL – Simple and Performant Security
Affected Version
<= 2.2.5.1
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-1504
View all SecuPress with Simple SSL – Simple and Performant Security vulnerabilities

At a glance

CVE-2024-1504 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the SecuPress with Simple SSL WordPress plugin, affecting versions <= 2.2.5.1. 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 2.2.5.2; sites on affected versions should update now. Disclosed April 2024, reported by Lucio Sá.

Vulnerability Overview

The SecuPress Free — WordPress Security plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.2.5.1. This is due to missing or incorrect nonce validation on the secupress_blackhole_ban_ip() function. This makes it possible for unauthenticated attackers to block a user's IP via a forged request granted they can trick the user 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)

SecuPress with Simple SSL <= 2.2.5.1 carries this weakness at secupress_blackhole_ban_ip(), 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 SecuPress with Simple SSL the fix is 2.2.5.2: builds <= 2.2.5.1 are affected, anything from 2.2.5.2 onward is not.

Remediation

Update to version 2.2.5.2, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-1504https://www.wordfence.com/threat-intel/vulnerabilities/id/4243bd6d-34f6-4d29-a333-4499a2e2d2e1https://nvd.nist.gov/vuln/detail/CVE-2024-1504

Related records

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