dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-9987

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Broadstreet WordPress plugin has an AJAX action 'get_sponsored_meta()' that fails to properly enforce authorization checks, allowing authenticated users with subscriber-level access to retrieve sensitive business details that are marked as password protected or private.

MitigationUpdate the plugin to a version beyond 1.53.1 that properly restricts the get_sponsored_meta() AJAX action to authorized users only, or implement proper capability checks on the vulnerable endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Broadstreet plugin is installed
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'Broadstreet' or 'Broadstreet Ads' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'broadstreet' or similar.
    Affected if The Broadstreet plugin appears in the installed plugins list
  2. Check installed plugin version
    In the Plugins page, locate the Broadstreet plugin and view its version number displayed beneath the plugin name. Compare this version number to the affected range (versions up to and including 1.53.1).
    Affected if The installed version is 1.53.1 or lower, or if no version is displayed and the plugin has not been updated recently
  3. Test AJAX endpoint accessibility
    Send a request to the vulnerable endpoint: access the URL 'https://your-site.com/wp-admin/admin-ajax.php?action=get_sponsored_meta' (replace your-site.com with your actual domain). Use a browser dev tools or curl with a low-privileged account (subscriber role) to see if the endpoint returns data.
    Affected if The endpoint returns sensitive business details (such as password-protected or private posts meta) without rejecting the request
  4. Verify WordPress user role exposure
    Log in with a test user who has only 'Subscriber' role. Attempt to access the get_sponsored_meta AJAX action. Check if the response contains data that should only be visible to higher-privileged users (administrators, editors).
    Affected if A subscriber-level user can retrieve data that is marked as private or password-protected through this AJAX endpoint

If the Broadstreet plugin version is 1.53.1 or lower AND the get_sponsored_meta AJAX endpoint is accessible to subscriber-level users without proper authorization, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 1.53.1 that properly restricts the get_sponsored_meta() AJAX action to authorized users only, or implement proper capability checks on the vulnerable endpoint.

Recommended fix Moderate confidence

Broadstreet plugin version 1.53.2 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Broadstreet plugin in the list
  4. Click 'Update now' if an update is available, or manually update to version 1.53.2 or higher
  5. Verify the update completed successfully

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9987 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9987 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data