CVE-2026-7051

Blog2Social: Social Media Auto Post & Scheduler <= 8.9.0 - Missing Authorization to Authenticated (Subscriber+) Delete Arbitrary B2S Post Records via 'postId' Parameter

2026-05-12 15:27
awhacken

Strategic Overview

Status
Patched in 8.9.1
Affected Plugin
Blog2Social: Social Media Auto Post & Scheduler
Affected Version
<= 8.9.0
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-7051
View all Blog2Social: Social Media Auto Post & Scheduler vulnerabilities

At a glance

CVE-2026-7051 is a medium-severity Missing Authorization vulnerability in the Blog2Social WordPress plugin, affecting versions <= 8.9.0. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 8.9.1; sites on affected versions should update now. Disclosed May 2026, reported by awhacken.

Vulnerability Overview

The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 8.9.0. This is due to a missing ownership verification in the B2S_Post_Tools::deleteUserPublishPost() and B2S_Post_Tools::deleteUserSchedPost() functions, neither function includes a blog_user_id constraint in its database query, allowing authenticated attackers to soft-delete any user's B2S post records by supplying arbitrary sequential wp_b2s_posts.id values via the 'postId' parameter. This makes it possible for authenticated attackers to delete other users' published and scheduled social media post records, disrupting content publishing workflows.

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

Blog2Social <= 8.9.0 carries this weakness at postId, and reaching it takes an account at Subscriber 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 8.9.1: builds <= 8.9.0 are affected, anything from 8.9.1 onward is not.

Remediation

Update to version 8.9.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 8.9.1 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-7051https://www.wordfence.com/threat-intel/vulnerabilities/id/f0859e21-851a-4a6d-aa6c-9f759c5866d9https://nvd.nist.gov/vuln/detail/CVE-2026-7051

Related records

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