# CVE-2025-14943: Missing authorization in Blog2Social: Social Media Auto Post & Scheduler

> Authenticated subscribers can access sensitive data from private or draft posts due to insufficient authorization checks in the Blog2Social plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-hxh3-g6p5-hhm6

## What is CVE-2025-14943?

CVE-2025-14943 is a medium-severity missing authorization vulnerability in pr-gateway Blog2Social: Social Media Auto Post & Scheduler, published on 10 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-14943?


## How do I fix CVE-2025-14943?

No fix has been published for CVE-2025-14943 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-14943 being exploited?

There is no known exploitation of CVE-2025-14943 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14943 and fix it if it is affected.

What it is: CVE-2025-14943 is a medium-severity missing authorization vulnerability in pr-gateway Blog2Social: Social Media Auto Post & Scheduler, published on 10 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14943 in the wild and no public exploit code.

Affected product: pr-gateway Blog2Social: Social Media Auto Post & Scheduler. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14943/ (Markdown: https://insights.sbomify.com/CVE-2025-14943/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14943
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14943
- OSV: https://osv.dev/vulnerability/CVE-2025-14943

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14943/
Summaries are generated and may contain mistakes; the official description above is the record.