# CVE-2026-1942: Missing authorization in Blog2Social: Social Media Auto Post & Scheduler

> Authenticated subscribers can modify arbitrary posts and pages due to missing capability checks in the Blog2Social WordPress plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 18 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-9pr5-g9xr-gp22

## What is CVE-2026-1942?

CVE-2026-1942 is a medium-severity missing authorization vulnerability in pr-gateway Blog2Social: Social Media Auto Post & Scheduler, published on 18 Feb 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 unauthorized modification of data due to a missing capability check on the b2s_curation_draft AJAX action in all versions up to, and including, 8.7.4. The curationDraft() function only verifies current_user_can('read') without checking whether the user has edit_post permission for the target post. Combined with the plugin granting UI access and nonce exposure to all roles, this makes it possible for authenticated attackers, with Subscriber-level access and above, to overwrite the title and content of arbitrary posts and pages by supplying a target post ID via the 'b2s-draft-id' parameter.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-1942?


## How do I fix CVE-2026-1942?

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

## Is CVE-2026-1942 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1942 and fix it if it is affected.

What it is: CVE-2026-1942 is a medium-severity missing authorization vulnerability in pr-gateway Blog2Social: Social Media Auto Post & Scheduler, published on 18 Feb 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-2026-1942 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-2026-1942/ (Markdown: https://insights.sbomify.com/CVE-2026-1942/index.md)
```

## Sources

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

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