Quick answers
- Is CVE-2026-89031 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-89031 being exploited in the wild.
- How severe is CVE-2026-89031?
- Medium severity, with a CVSS score of 5.4, published 16 September 2026.
- Which products and versions are affected?
- Adenion Blog2Social before 9.1.0.
- Is there a fix for CVE-2026-89031?
- 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-89031 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-89031?
- Check whether you run Adenion Blog2Social 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 vulnerability is a broken access control issue (CWE-639) in the b2s_calendar_move_post AJAX handler within includes/Ajax/Post.php. The handler performs UPDATE operations on the b2s_posts table using only the attacker-supplied b2s_id primary key without validating that the requesting user owns the record via a blog_user_id constraint. Any authenticated user with the edit_posts WordPress capability can manipulate scheduled post records belonging to other users, altering publication state, suppressing posts, or rescheduling them. The vulnerability requires network access and valid WordPress authentication with edit_posts capability, but no additional user interaction. The issue is patched in version 9.1.0.
Affected products
- Adenion Blog2Social before 9.1.0
Timeline
- 2026-09-16: disclosed