Blog2Social: Social Media Auto Post & Scheduler <= 9.1.0 - Missing Authorization to Authenticated (Contributor+) Arbitrary Modification via Multiple AJAX Handlers
Strategic Overview
- Status
- Patched in 9.1.1
- Affected Plugin
- Blog2Social: Social Media Auto Post & Scheduler
- Affected Version
<= 9.1.0- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-92829
At a glance
CVE-2026-92829 is a medium-severity Missing Authorization vulnerability in the Blog2Social WordPress plugin, affecting versions <= 9.1.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 9.1.1; sites on affected versions should update now. Disclosed September 2026, reported by Averon Averenkov (Averon Averenkov).
Vulnerability Overview
The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 9.1.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to view, modify, or delete other users' Blog2Social records, including disclosing another user's network authentication IDs and scheduled post content, overwriting Open Graph and Twitter Card post metadata on posts they do not own, rebinding another user's social-network authorization, and mass-hiding all users' scheduled posts sitewide. The plugin's b2s_security_nonce is emitted on the post-edit meta box, which Contributors can render, making the nonce available to any authenticated user at that role level or above.
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-862: Missing Authorization
Reaching this weakness in Blog2Social <= 9.1.0 takes an account at Contributor level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Blog2Social the fix is 9.1.1: builds <= 9.1.0 are affected, anything from 9.1.1 onward is not.
Remediation
Update to version 9.1.1, 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 9.1.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 6.5CVE-2026-1942: Blog2Social Authenticated (Subscriber+) Arbitrary Post
CVE-2026-1942 - 5.4CVE-2026-7051: Blog2Social Authenticated (Subscriber+) Delete
CVE-2026-7051 - 5.4CVE-2025-13558: Blog2Social Authenticated (Subscriber+) Arbitrary
CVE-2025-13558 - 5.3CVE-2024-3678: Blog2Social Information Exposure
CVE-2024-3678
Other vulnerabilities in Blog2Social: Social Media Auto Post & Scheduler
- 9.9CVE-2024-3549: Blog2Social SQL Injection
CVE-2024-3549 - 9.8CVE-2019-13572: Blog2Social SQL Injection
CVE-2019-13572 - 8.8CVE-2022-3246: Blog2Social <= 6.9.9 SQL Injection
CVE-2022-3246 - 8.8CVE-2021-24137: Blog2Social SQL Injection
CVE-2021-24137 - 8.5Blog2Social <= 6.9.3 PHP Object Injection
- 7.4Blog2Social: Social Media Auto Post & Scheduler PHP Object Injection
- 7.2CVE-2026-56044: Blog2Social Stored XSS
CVE-2026-56044 - 6.8CVE-2022-3247: Blog2Social <= 6.9.9 Server-Side Request Forgery
CVE-2022-3247
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C