Strategic Overview
- Status
- Patched in 1.52.2
- Affected Plugin
- Broadstreet
- Affected Version
<= 1.51.1- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-32270
At a glance
CVE-2025-32270 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Broadstreet WordPress plugin, affecting versions <= 1.51.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 1.52.2; sites on affected versions should update now. Disclosed April 2025, reported by Nguyen Xuan Chien.
Vulnerability Overview
The Broadstreet plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.51.1. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action 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)
Reaching this weakness in Broadstreet <= 1.51.1 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 Broadstreet the fix is 1.52.2: builds <= 1.51.1 are affected, anything from 1.52.2 onward is not.
Remediation
Update to version 1.52.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Broadstreet: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Broadstreet 1.52.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Broadstreet
- 6.4CVE-2025-48113: Broadstreet <= 1.51.2 Stored Cross-Site Scripting
CVE-2025-48113 - 6.4CVE-2025-32211: Broadstreet <= 1.52.1 Stored Cross-Site Scripting
CVE-2025-32211 - 6.4CVE-2024-11825: Broadstreet <= 1.51.0 Stored Cross-Site Scripting
CVE-2024-11825 - 6.1CVE-2025-4652: Broadstreet Ads <= 1.51.7 Reflected XSS
CVE-2025-4652 - 5.3CVE-2025-9987: Broadstreet <= 1.53.1 Information Disclosure
CVE-2025-9987 - 4.4CVE-2025-9989: Broadstreet <= 1.53.1 Stored Cross-Site Scripting
CVE-2025-9989 - 4.3CVE-2026-1881: Broadstreet <= 1.52.2 Private Post Meta Disclosure
CVE-2026-1881 - 4.3CVE-2025-9988: Broadstreet Authenticated (Subscriber+) Advertiser
CVE-2025-9988
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C