CVE-2025-9987

Broadstreet <= 1.53.1 - Authenticated (Subscriber+) Information Disclosure

2026-05-12 15:29

Strategic Overview

Status: Patched in 1.53.2
Affected Plugin: Broadstreet
Affected Version: <= 1.53.1
CVSS: 5.3Medium
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE-2025-9987

At a glance

CVE-2025-9987 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Broadstreet WordPress plugin, affecting versions <= 1.53.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.53.2; sites on affected versions should update now. Disclosed May 2026, reported by greenhats.

Vulnerability Overview

The Broadstreet plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.53.1 via the get_sponsored_meta() AJAX action. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract data from password protected and private business details.

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, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Broadstreet <= 1.53.1 carries this weakness at get_sponsored_meta(), and reaching it takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Broadstreet the fix is 1.53.2: builds <= 1.53.1 are affected, anything from 1.53.2 onward is not.

Remediation

Update to version 1.53.2, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Broadstreet 1.53.2 closes this, and updating the plugin is the step that ends it.

Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-9987 https://www.wordfence.com/threat-intel/vulnerabilities/id/b3cc3835-25f5-43b3-82be-397b8b3bd369 https://nvd.nist.gov/vuln/detail/CVE-2025-9987

Related records

Other vulnerabilities in Broadstreet

CVSS Vector

5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityLow
IntegrityNone
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/