# CVE-2026-94505: Missing authorization in Nelio Content – Editorial Calendar & Social Media Auto-Posting

> Authenticated contributors can delete arbitrary reusable social messages due to missing authorization checks in the Nelio Content plugin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **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:** 3 Oct 2026
- **Updated:** 3 Oct 2026
- **Also known as:** GHSA-j2j8-hvh9-q6jf

## What is CVE-2026-94505?

CVE-2026-94505 is a high-severity missing authorization vulnerability in Nelio Content – Editorial Calendar & Social Media Auto-Posting, published on 3 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Nelio Content – Editorial Calendar & Social Media Auto-Posting plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.5.0 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to permanently delete any reusable social message (nc_reusable_social post), including those authored by administrators or other privileged users.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-94505 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94505 is a high-severity missing authorization vulnerability in Nelio Content – Editorial Calendar & Social Media Auto-Posting, published on 3 Oct 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-94505 in the wild and no public exploit code.

Affected product: Nelio Content – Editorial Calendar & Social Media Auto-Posting. 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-94505/ (Markdown: https://insights.sbomify.com/CVE-2026-94505/index.md)
```

## Sources

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

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