Nelio Content <= 4.5.0 - Missing Authorization to Authenticated (Contributor+) Arbitrary Reusable Message Deletion via 'id' Parameter
Strategic Overview
- Status
- Patched in 4.5.1
- Affected Version
<= 4.5.0- CVSS
- 8.1High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-94505
At a glance
CVE-2026-94505 is a high-severity Missing Authorization vulnerability in the Nelio Content WordPress plugin, affecting versions <= 4.5.0. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 4.5.1; sites on affected versions should update now. Disclosed October 2026, reported by Wordfence PRISM.
Vulnerability Overview
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.
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. A successful exploit has high impact on integrity, availability.
CWE-862: Missing Authorization
Reaching this weakness in Nelio Content <= 4.5.0 takes an account at Contributor level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Nelio Content the fix is 4.5.1: builds <= 4.5.0 are affected, anything from 4.5.1 onward is not.
Remediation
Update to version 4.5.1, 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: Nelio Content 4.5.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Nelio Content – Editorial Calendar & Social Media Auto-Posting
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C