Blog2Social Plugin up to 9.1.4 on WordPress AJAX Handlers b2s_ship_item/b2s_ship_item_reload_url postId resource injection

Summaryinfo

A vulnerability was found in Blog2Social Plugin up to 9.1.4. It has been classified as problematic. The impacted element is the function b2s_ship_item/b2s_ship_item_reload_url of the component AJAX Handlers. Performing a manipulation of the argument postId results in resource injection. This vulnerability is reported as CVE-2026-108092. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Blog2Social Plugin up to 9.1.4. This affects the function b2s_ship_item/b2s_ship_item_reload_url of the component AJAX Handlers. The manipulation of the argument postId with an unknown input leads to a resource injection vulnerability. CWE is classifying the issue as CWE-99. The product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control. This is going to have an impact on confidentiality. The summary by CVE is:

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.

The advisory is shared at wordfence.com. This vulnerability is uniquely identified as CVE-2026-108092 since 10/09/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/15/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-101926). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• WordPress Plugin

Name

• Blog2Social Plugin

Version

• 9.1.0
• 9.1.1
• 9.1.2
• 9.1.3
• 9.1.4

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion