CVE-2026-108092

Social Media Auto Post & Scheduler <= 9.1.4 - Authenticated (Contributor+) Insecure Direct Object Reference to Sensitive Information Exposure

2026-10-14 18:54
Kazuma Matsumoto

Strategic Overview

Status
Patched in 9.1.5
Affected Plugin
Blog2Social: Social Media Auto Post & Scheduler
Affected Version
<= 9.1.4
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-108092
View all Blog2Social: Social Media Auto Post & Scheduler vulnerabilities

At a glance

CVE-2026-108092 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Blog2Social WordPress plugin, affecting versions <= 9.1.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 9.1.5; sites on affected versions should update now. Disclosed October 2026, reported by Kazuma Matsumoto.

Vulnerability Overview

The Blog2Social – Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 9.1.4. This is due to the b2s_ship_item and b2s_ship_item_reload_url AJAX handlers lacking per-object authorization on the postId parameter. This makes it possible for authenticated attackers with Contributor-level access and above to read the title and content of any post, including private and pending posts belonging to other users.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Blog2Social <= 9.1.4 takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Blog2Social the fix is 9.1.5: builds <= 9.1.4 are affected, anything from 9.1.5 onward is not.

Remediation

Update to version 9.1.5, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Blog2Social 9.1.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-108092https://www.wordfence.com/threat-intel/vulnerabilities/id/b394ee3e-fc1c-40b5-b3c5-a9b5e44a7a14https://nvd.nist.gov/vuln/detail/CVE-2026-108092

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C