CVE-2024-7423

Stream <= 4.0.1 - Cross-Site Request Forgery to Arbitrary Options Update

2024-09-12 00:00
vgo0

Strategic Overview

Status
Patched in 4.0.2
Affected Plugin
Stream – Activity Log & Audit Trail
Affected Version
<= 4.0.1
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-7423
View all Stream – Activity Log & Audit Trail vulnerabilities

At a glance

CVE-2024-7423 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Stream WordPress plugin, affecting versions <= 4.0.1. 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 4.0.2; sites on affected versions should update now. Disclosed September 2024, reported by vgo0.

Vulnerability Overview

The Stream plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.0.1. This is due to missing or incorrect nonce validation on the network_options_action() function. This makes it possible for unauthenticated attackers to update arbitrary options that can lead to DoS or privilege escalation 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

Stream <= 4.0.1 carries this weakness at network_options_action(), 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 Stream the fix is 4.0.2: builds <= 4.0.1 are affected, anything from 4.0.2 onward is not.

Remediation

Update to version 4.0.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Stream: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Stream 4.0.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-7423https://www.wordfence.com/threat-intel/vulnerabilities/id/9d15e418-36bb-4f53-ac67-8f6122591dd2https://nvd.nist.gov/vuln/detail/CVE-2024-7423

Related records

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