Is CVE-2026-7051 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-7051 being exploited in the wild.

How severe is CVE-2026-7051?

Medium severity, with a CVSS score of 5.4, published 13 May 2026.

Which products and versions are affected?

Blog2Social: Social Media Auto Post & Scheduler up to, and including, 8.9.0.

Is there a fix for CVE-2026-7051?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-7051 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-7051?

Check whether you run Blog2Social: Social Media Auto Post & Scheduler at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-7051: Blog2Social WordPress plugin missing authorization in post deletion functions

CVE-2026-7051 · Severity: medium · CVSS 5.4 · Published 2026-05-13

The Blog2Social plugin for WordPress, which automates social media posting, contains a security flaw that allows logged-in users to delete social media posts scheduled or published by other users. This could lead to unauthorized removal of content and disruption of a company's social media marketing workflows. An attacker only needs basic account access to the WordPress site to exploit this issue.

Technologies: Blog2Social: Social Media Auto Post & Scheduler. Vendors: Blog2Social.

Quick answers

Is CVE-2026-7051 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-7051 being exploited in the wild.
How severe is CVE-2026-7051?: Medium severity, with a CVSS score of 5.4, published 13 May 2026.
Which products and versions are affected?: Blog2Social: Social Media Auto Post & Scheduler up to, and including, 8.9.0.
Is there a fix for CVE-2026-7051?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-7051 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-7051?: Check whether you run Blog2Social: Social Media Auto Post & Scheduler at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The Blog2Social plugin for WordPress is vulnerable to an Insecure Direct Object Reference (IDOR) / Missing Authorization flaw in the B2S_Post_Tools::deleteUserPublishPost() and B2S_Post_Tools::deleteUserSchedPost() functions. These functions fail to include a 'blog_user_id' constraint in their database queries, meaning they do not verify if the user requesting the deletion actually owns the record. An authenticated attacker can exploit this by providing arbitrary sequential values to the 'postId' parameter, allowing them to soft-delete published or scheduled social media post records belonging to any other user. The vulnerability is present in all versions up to 8.9.0.

Affected products

Blog2Social Blog2Social: Social Media Auto Post & Scheduler up to, and including, 8.9.0

Timeline

2026-05-13: disclosed
2026-05-13: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.