Skip to main content
VulnerabilityPublished Updated

CVE-2026-89031: Blog2Social (WordPress plugin) · Insecure Direct Object Reference

Affects Blog2Social (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 9.1.0 when convenient.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 9.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Blog2Social (WordPress plugin) to 9.1.0.

Affected software

ProductAffectedFixed in
AdenionBlog2SocialAffected
  • <9.1.0
Fixed in
  • 9.1.0

AI-suggested

Upgrade the Blog2Social plugin to version 9.1.0 or later where this authorization bypass vulnerability is fixed. Patch status is not explicitly confirmed in the provided data, but the affected versions are prior to 9.1.0, implying the fix is in 9.1.0. Until patched, restrict edit_posts capability to trusted users only.

Description

Adenion Blog2Social plugin for WordPress before 9.1.0 allows low-privileged users to modify the scheduled post records of other users. The b2s_calendar_move_post AJAX handler in includes/Ajax/Post.php issues an UPDATE against the b2s_posts table using only the attacker-supplied b2s_id primary key with no blog_user_id ownership constraint, allowing any user with the edit_posts capability to reschedule, suppress, or alter the publication state of any other user's scheduled social media post.

References

Community reviews

Loading reviews…