# CVE-2026-2126: Missing authorization in User Submitted Posts – Enable Users to Submit Posts from the Front End

> Unauthenticated attackers can bypass category restrictions to assign posts to arbitrary categories in the User Submitted Posts WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-pm8v-w3f2-2hxx

## What is CVE-2026-2126?

CVE-2026-2126 is a medium-severity missing authorization vulnerability in specialk User Submitted Posts – Enable Users to Submit Posts from the Front End, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The User Submitted Posts – Enable Users to Submit Posts from the Front End plugin for WordPress is vulnerable to Incorrect Authorization in all versions up to, and including, 20260113. This is due to the `usp_get_submitted_category()` function accepting user-submitted category IDs from the POST body without validating them against the admin-configured allowed categories stored in `usp_options['categories']`. This makes it possible for unauthenticated attackers to assign submitted posts to arbitrary categories, including restricted ones, by crafting a direct POST request with manipulated `user-submitted-category[]` values, bypassing the frontend category restrictions.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-2126 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2126 is a medium-severity missing authorization vulnerability in specialk User Submitted Posts – Enable Users to Submit Posts from the Front End, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2126 in the wild and no public exploit code.

Affected product: specialk User Submitted Posts – Enable Users to Submit Posts from the Front End. 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-2126/ (Markdown: https://insights.sbomify.com/CVE-2026-2126/index.md)
```

## Sources

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

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