LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2126: User Submitted Posts <= 20260113 - Incorrect Authorization to Unauthenticated Category Restriction Bypass via 'user-submitted-category' Parameter

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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-2126 affects the WordPress User Submitted Posts plugin. Unauthenticated visitors can bypass configured front-end category restrictions and place submitted posts into categories that site administrators intended to restrict. This is an integrity issue, not a data theft or service outage issue based on the published CVSS.

Executive priority

Treat as a moderate-priority WordPress integrity issue. It is unlikely to cause direct data loss, but it can undermine publishing controls and moderation workflows. Prioritize sites where public submissions feed visible content, restricted categories, SEO workflows, or compliance-sensitive publishing processes.

Technical view

The plugin’s usp_get_submitted_category() accepts category IDs from POST data without validating them against admin-configured allowed categories in usp_options['categories']. Versions up to and including 20260113 are described as vulnerable. The issue is CWE-863, incorrect authorization, with CVSS 3.1 score 5.3, network exploitable and unauthenticated.

Likely exposure

Exposure is limited to WordPress sites using this plugin with front-end post submissions enabled, especially where category restrictions are part of moderation, publishing workflow, or content governance. Sites not using the plugin, or not relying on category restrictions, have lower practical impact.

Exploitation context

The CVE states exploitation requires a crafted direct POST request and no authentication. CISA KEV is false in the provided data, and no cited source states active exploitation. Impact is limited to unauthorized category assignment for submitted posts.

Researcher notes

Key evidence is the CVE description, Wordfence advisory, WordPress Trac references, and a related changeset. The affected-range data is inconsistent in the bundle, but the narrative states all versions up to and including 20260113. No public source in the bundle confirms active exploitation.

Mitigation direction

  • Check vendor or WordPress plugin guidance for a fixed release beyond 20260113.
  • Update the User Submitted Posts plugin when a fixed version is available.
  • Temporarily disable front-end submissions if restricted categories are business-critical.
  • Moderate submitted posts before publication, especially category assignment.
  • Review plugin configuration for allowed categories and publishing workflow assumptions.

Validation and detection

  • Inventory WordPress sites for the User Submitted Posts plugin.
  • Flag installations at version 20260113 or earlier as potentially affected.
  • Confirm whether front-end post submission is enabled.
  • Review whether restricted categories carry business, compliance, or editorial impact.
  • After remediation, verify submissions cannot use categories outside the configured allowed list.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2126 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-2126Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
specialkUser Submitted Posts – Enable Users to Submit Posts from the Front End0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.