CVE-2025-69311
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 · uneditedMissing Authorization vulnerability in Broadstreet Broadstreet Ads broadstreet allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Broadstreet Ads: from n/a through <= 1.52.1.
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 · moderate confidenceThe Broadstreet Ads WordPress plugin versions through 1.52.1 contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This is a broken access control issue where the plugin fails to properly verify user permissions before allowing access to certain functionality.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Broadstreet Ads plugin is installedLocate the plugin directory at wp-content/plugins/broadstreet-ads/ or run: wp plugin list --name=broadstreet-adsAffected if Plugin directory exists in wp-content/plugins/
-
Identify installed plugin versionRead the main plugin file header (e.g., broadstreet-ads.php) and locate the 'Version:' tag, or run: wp plugin get broadstreet-ads --field=versionAffected if Version number is 1.52.1 or lower (all versions through 1.52.1 are affected)
-
Verify plugin is activeCheck wp_options table for option_name='active_plugins' containing 'broadstreet-ads', or run: wp plugin is-active broadstreet-adsAffected if Plugin appears in the list of active plugins on the site
-
Audit user capabilities and administrative accountsReview WordPress user list (wp-admin/users.php) for unexpected administrators, or query wp_usermeta for users with wp_capabilities containing 'administrator' that you do not recognizeAffected if Unexpected administrative accounts exist that were not created by known site administrators
-
Check for unauthorized plugin functionality accessReview server access logs for requests to /wp-admin/admin-ajax.php?action=broadstreet* or plugin-specific AJAX endpoints that may have been accessed by non-administrator usersAffected if Non-administrative users have accessed Broadstreet Ads AJAX actions or admin functionality
A site is affected if the Broadstreet Ads plugin is installed, active, and running version 1.52.1 or lower, exposing functionality without proper permission checks.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate Broadstreet Ads to the latest patched version. If no patch is available, disable the plugin until proper authorization controls are implemented and verified.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69311 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-69311 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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