Smash Balloon Social Post Feed <= 4.3.2 - Missing Authorization
Strategic Overview
- Status
- Patched in 4.3.3
- Affected Version
<= 4.3.2- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-49937
At a glance
CVE-2025-49937 is a medium-severity Missing Authorization vulnerability in the Smash Balloon Social Post Feed WordPress plugin, affecting versions <= 4.3.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 4.3.3; sites on affected versions should update now. Disclosed October 2025, reported by Legion Hunter.
Vulnerability Overview
The Smash Balloon Social Post Feed – Simple Social Feeds for WordPress plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 4.3.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform an unauthorized action.
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 interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in Smash Balloon Social Post Feed <= 4.3.2 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Smash Balloon Social Post Feed the fix is 4.3.3: builds <= 4.3.2 are affected, anything from 4.3.3 onward is not.
Remediation
Update to version 4.3.3, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Smash Balloon Social Post Feed 4.3.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Smash Balloon Social Post Feed – Simple Social Feeds for WordPress
- 6.4CVE-2026-16775: Smash Balloon Social Post Feed <= 4.9.0 Stored XSS
CVE-2026-16775 - 6.4CVE-2025-4577: Smash Balloon Custom Facebook Feed <= 4.3.1 Stored XSS
CVE-2025-4577 - 6.4CVE-2022-4477: Smash Balloon Social Post Feed <= 4.1.5 Stored XSS
CVE-2022-4477 - 6.1CVE-2021-24508: Smash Balloon Social Post Feed <= 2.19.1 Stored XSS
CVE-2021-24508 - 6.1Smash Balloon Plugins (Various Versions) Reflected XSS
- 5.4CVE-2021-25065: Smash Balloon Social Post Feed <= 4.1 Reflected XSS
CVE-2021-25065 - 5.4CVE-2021-24918: Smash Balloon… Arbitrary Plugin Settings Update
CVE-2021-24918 - 4.3CVE-2024-31379: Smash Balloon Social Post Feed <= 4.2.1 CSRF
CVE-2024-31379
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C