pr-gateway Blog2Social Plugin up to 8.9.0 on WordPress Database Query deleteUserSchedPost postId authorization

Summaryinfo

A vulnerability classified as critical was found in pr-gateway Blog2Social Plugin up to 8.9.0 on WordPress. The affected element is the function B2S_Post_Tools::deleteUserPublishPost/B2S_Post_Tools::deleteUserSchedPost of the component Database Query Handler. The manipulation of the argument postId results in authorization. This vulnerability was named CVE-2026-7051. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as critical, was found in pr-gateway Blog2Social Plugin up to 8.9.0 on WordPress. Affected is the function B2S_Post_Tools::deleteUserPublishPost/B2S_Post_Tools::deleteUserSchedPost of the component Database Query Handler. The manipulation of the argument postId with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The weakness was presented by Nicky Dev. The advisory is shared for download at wordfence.com. This vulnerability is traded as CVE-2026-7051 since 04/25/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 05/13/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• pr-gateway

Name

• Blog2Social Plugin

Version

• 8.0
• 8.1
• 8.2
• 8.3
• 8.4
• 8.5
• 8.6
• 8.7
• 8.8
• 8.9.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion