CVE-2026-1881

Broadstreet <= 1.52.2 - Authenticated (Subscriber+) Private Post Meta Disclosure via get_sponsored_meta

2026-05-20 13:15
Tarcísio Luchesi De Almeida Silva (Poystick)

Strategic Overview

Status
Patched in 1.53.2
Affected Plugin
Broadstreet
Affected Version
<= 1.52.2
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-1881
View all Broadstreet vulnerabilities

At a glance

CVE-2026-1881 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Broadstreet WordPress plugin, affecting versions <= 1.52.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.53.2; sites on affected versions should update now. Disclosed May 2026, reported by Tarcísio Luchesi De Almeida Silva (Poystick).

Vulnerability Overview

The Broadstreet plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.52.2 via the get_sponsored_meta AJAX action due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to disclose any private post metadata.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Broadstreet <= 1.52.2 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Broadstreet the fix is 1.53.2: builds <= 1.52.2 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?

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: Broadstreet 1.53.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-1881https://www.wordfence.com/threat-intel/vulnerabilities/id/328ccf8f-797b-4b1a-b0f1-afd8e44f41e6https://nvd.nist.gov/vuln/detail/CVE-2026-1881

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C