Blog2Social: Social Media Auto Post & Scheduler Vulnerability (CVE-2026-4330)

On this page

Security Alert Summary

The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress has an authorization bypass vulnerability that allows authenticated users with Subscriber-level access and above to act on scheduled social posts that do not belong to them. The plugin’s AJAX handlers fail to verify ownership of a user-supplied b2s_id parameter before performing update and delete operations, which can lead to modification, rescheduling, or deletion of other users’ scheduled posts.


CVE Details

  • CVE ID: CVE-2026-4330
  • Affected component: Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress
  • Affected versions: All versions up to, and including, 8.8.3
  • Published: April 8, 2026 at 8:16:23 AM
  • Last modified: April 8, 2026 at 8:16:23 AM
  • CVSS v3.1 base score: 4.3 (MEDIUM)
  • CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
  • Authentication / privileges / user interaction: Vulnerability requires an authenticated user with low privileges (Subscriber-level or higher). No user interaction is required.
  • Primary impact: Confidentiality: None; Integrity: Low (modification or deletion of scheduled posts); Availability: None
  • CWE / weakness: CWE-639

Technical Details

The vulnerability is an authorization bypass caused by the plugin’s AJAX handlers failing to confirm that a provided b2s_id value belongs to the currently authenticated user before performing UPDATE and DELETE operations. Because the ownership check is missing or insufficient, an authenticated user can supply another user’s b2s_id and cause the plugin to act on scheduled posts that belong to that other user.

The description identifies the issue in the plugin’s AJAX handling logic; related code paths include the handlers that process requests to update or remove scheduled social posts. The direct consequence is unauthorized modification, rescheduling, or deletion of scheduled posts belonging to different accounts within the same WordPress site.


How This Could Impact Your Website

Consider a site with multiple editors, contributors, or external contractors who schedule social posts through Blog2Social. An authenticated user with Subscriber-level access could, by providing a manipulated b2s_id, modify or delete scheduled posts created by other users. For a site owner or site manager this can mean unexpected changes to the social posting calendar, missed promotions, or posts deleted before they publish.

Practical consequences include reduced integrity of your social publishing workflow and increased risk of targeted social engineering if attackers use altered or rescheduled posts to confuse staff or third-party partners. While the CVSS data indicates no confidentiality impact from this issue alone, tampered posts can still harm reputation or coordination across teams.

If you’re unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review.


Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, especially contributors and subscribers who do not need scheduling capabilities.
  • Enforce strong passwords and two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins from your site.
  • Monitor site activity and plugin logs for unusual updates, deletions, or scheduling changes.

If you’d like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.


References