CVE-2026-4330

Blog2Social: Social Media Auto Post & Scheduler <= 8.8.3 - Authenticated (Subscriber+) Insecure Direct Object Reference to Arbitrary Post Schedule Modification via 'b2s_id' Parameter

2026-04-07 19:13
s00me00ne

Strategic Overview

Status
Patched in 8.8.4
Affected Plugin
Blog2Social: Social Media Auto Post & Scheduler
Affected Version
<= 8.8.3
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-4330
View all Blog2Social: Social Media Auto Post & Scheduler vulnerabilities

At a glance

CVE-2026-4330 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Blog2Social WordPress plugin, affecting versions <= 8.8.3. 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 8.8.4; sites on affected versions should update now. Disclosed April 2026, reported by s00me00ne.

Vulnerability Overview

The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to authorization bypass through user-controlled key in all versions up to, and including, 8.8.3. This is due to the plugin's AJAX handlers failing to validate that the user-supplied 'b2s_id' parameter belongs to the current user before performing UPDATE and DELETE operations. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify, reschedule, or delete other users' scheduled social media posts.

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

Blog2Social <= 8.8.3 carries this weakness at b2s_id, and reaching it 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 Blog2Social the fix is 8.8.4: builds <= 8.8.3 are affected, anything from 8.8.4 onward is not.

Remediation

Update to version 8.8.4, 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: Blog2Social 8.8.4 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-4330https://www.wordfence.com/threat-intel/vulnerabilities/id/f3eec9c6-fef9-4d6e-8328-51efb997c99chttps://nvd.nist.gov/vuln/detail/CVE-2026-4330

Related records

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