CVE-2026-7051 MEDIUM

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

Vendor Pr-Gateway
Product Blog2Social: Social Media Auto Post & Scheduler
Weakness CWE-862 · Missing authorization
Published May 13, 2026
Last update May 13, 2026

CVSS base score

5.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Blog2Social versions up to 8.9.0 lack proper authorization checks, allowing authenticated users to modify or disable site functionality without proper permission. An attacker with a low-privilege account can alter settings or data that should be restricted to administrators. Update to a version newer than 8.9.0 to resolve this issue.

What an attacker can do

03Attacker Capabilities

Modify or disable site features and data without proper admin permission.

Potential impact on your site

04Site Impact

Unauthorized users can alter plugin settings, potentially disrupting social media posting or other core functionality.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege user account on the site.

Key dates

06Disclosure timeline

May 13, 2026 CVE published
May 13, 2026 Record updated