CVE-2025-14943

Blog2Social: Social Media Auto Post & Scheduler <= 8.7.2 - Incorrect Authorization to Authenticated (Subscriber+) Sensitive Information Exposure

2026-01-09 00:00
theviper17y

Strategic Overview

Status
Patched in 8.7.3
Affected Plugin
Blog2Social: Social Media Auto Post & Scheduler
Affected Version
<= 8.7.2
CVSS
4.3Medium
Weakness type
CWE-863 · Incorrect Authorization
CVE
CVE-2025-14943
View all Blog2Social: Social Media Auto Post & Scheduler vulnerabilities

At a glance

CVE-2025-14943 is a medium-severity Incorrect Authorization vulnerability in the Blog2Social WordPress plugin, affecting versions <= 8.7.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 8.7.3; sites on affected versions should update now. Disclosed January 2026, reported by theviper17y.

Vulnerability Overview

The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 8.7.2. This is due to a misconfigured authorization check on the 'getShipItemFullText' function which only verifies that a user has the 'read' capability (Subscriber-level) and a valid nonce, but fails to verify whether the user has permission to access the specific post being requested. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract data from password-protected, private, or draft posts.

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-863: Incorrect Authorization

Blog2Social <= 8.7.2 carries this weakness at getShipItemFullText, and reaching it takes an account at Subscriber level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.

The action runs for users the code intended to exclude, with the same effect as having no check at all. For Blog2Social the fix is 8.7.3: builds <= 8.7.2 are affected, anything from 8.7.3 onward is not.

Remediation

Update to version 8.7.3, 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 8.7.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-14943https://www.wordfence.com/threat-intel/vulnerabilities/id/7374db91-4e7d-4db2-9c58-bb9bdda5c85dhttps://nvd.nist.gov/vuln/detail/CVE-2025-14943

Related records

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