CVE-2026-4330 json
Blog2Social: Social Media Auto Post & Scheduler <= 8.8.3 - Authenticated (Subscriber+) Insecure Direct Object Reference to Arbitrary Post Schedule Modification via 'b2s_id' Parameter
published 2026-04-08 7 mo ago modified 2026-07-24 3 mo ago also EUVD-2026-20125
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected products
- pr-gateway Blog2Social: Social Media Auto Post & Scheduler
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/f3eec9c6-fef9-4d6e-8328-51efb997c99c?source=cve
- plugins.trac.wordpress.org /browser/blog2social/trunk/includes/Ajax/Post.php#L2183
- plugins.trac.wordpress.org /browser/blog2social/tags/8.8.2/includes/Ajax/Post.php#L2183
- plugins.trac.wordpress.org /browser/blog2social/trunk/includes/Ajax/Post.php#L2273
- plugins.trac.wordpress.org /browser/blog2social/tags/8.8.2/includes/Ajax/Post.php#L2273
- plugins.trac.wordpress.org /browser/blog2social/trunk/includes/Ajax/Post.php#L2322
- plugins.trac.wordpress.org /browser/blog2social/tags/8.8.2/includes/Ajax/Post.php#L2322
- plugins.trac.wordpress.org /browser/blog2social/trunk/includes/B2S/Post/Tools.php#L32
- plugins.trac.wordpress.org /browser/blog2social/tags/8.8.2/includes/B2S/Post/Tools.php#L32
- plugins.trac.wordpress.org /browser/blog2social/trunk/includes/B2S/Ship/Save.php#L190
- plugins.trac.wordpress.org /browser/blog2social/tags/8.8.2/includes/B2S/Ship/Save.php#L190
- plugins.trac.wordpress.org /browser/blog2social/trunk/includes/Ajax/Post.php#L2178
- plugins.trac.wordpress.org /browser/blog2social/tags/8.8.2/includes/Ajax/Post.php#L2178
- plugins.trac.wordpress.org /browser/blog2social/trunk/includes/Loader.php#L2202
- plugins.trac.wordpress.org /browser/blog2social/tags/8.8.2/includes/Loader.php#L2202
- plugins.trac.wordpress.org /changeset/3494550/
Sources
- CVE List CVE-2026-4330
- NVD CVE-2026-4330
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.