CVE-2024-31379

Smash Balloon Social Post Feed <= 4.2.1 - Cross-Site Request Forgery

2024-04-10 00:00
Majed Refaea

Strategic Overview

Status
Patched in 4.2.2
Affected Plugin
Smash Balloon Social Post Feed – Simple Social Feeds for WordPress
Affected Version
<= 4.2.1
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-31379
View all Smash Balloon Social Post Feed – Simple Social Feeds for WordPress vulnerabilities

At a glance

CVE-2024-31379 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Smash Balloon Social Post Feed WordPress plugin, affecting versions <= 4.2.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 4.2.2; sites on affected versions should update now. Disclosed April 2024, reported by Majed Refaea.

Vulnerability Overview

The Smash Balloon Social Post Feed plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.2.1. This is due to missing or incorrect nonce validation on the maybe_source_connection_data() function. This makes it possible for unauthenticated attackers to check connection 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)

Smash Balloon Social Post Feed <= 4.2.1 carries this weakness at maybe_source_connection_data(), 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 Smash Balloon Social Post Feed the fix is 4.2.2: builds <= 4.2.1 are affected, anything from 4.2.2 onward is not.

Remediation

Update to version 4.2.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Smash Balloon Social Post Feed: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Smash Balloon Social Post Feed 4.2.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-31379https://www.wordfence.com/threat-intel/vulnerabilities/id/623b139e-c5a1-4d2e-b05c-72707f421ef8https://nvd.nist.gov/vuln/detail/CVE-2024-31379

Related records

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