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.
CVE-2026-89031
Score 5.4 from GitHub Security Advisory published 2026-09-16. a secondary CVSS source baseline 5.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(high)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity54% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 16, 2026
Advisory Details (2)
Auto-updated Sep 16, 2026Blog2Social WordPress Plugin < 9.1.0 Broken Access Control via b2s_calendar_move_post | Advisories | VulnCheck
https://www.vulncheck.com/advisories/blog2social-wordpress-plugin-broken-access-control-via-b2s-calendar-move-postBlog2Social: Social Media Auto Post & Scheduler – WordPress plugin | WordPress.org
https://wordpress.org/plugins/blog2social/#developersVendor Advisories for CVE-2026-89031(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 19:12 UTCGHSA enrichment
- 2026-09-19 18:14 UTCEG score recompute
- 2026-09-19 18:14 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 17:16 UTCEG score recompute
- 2026-09-18 17:16 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 16:18 UTCEG score recompute
- 2026-09-17 16:18 UTCGHSA enrichment
- 2026-09-16 15:20 UTCEG score recompute
- 2026-09-16 14:26 UTCEG score recompute
- 2026-09-16 14:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
Frequently asked(5)
What is CVE-2026-89031?
When was CVE-2026-89031 disclosed?
Is CVE-2026-89031 actively exploited?
What is the CVSS score of CVE-2026-89031?
How do I remediate CVE-2026-89031?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-89031
Is Your Infrastructure Affected by CVE-2026-89031?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.