CVE-2026-2126
Incorrect Authorization in WordPress User Submitted Posts Plugin
Publication date: 2026-02-18
Last updated on: 2026-02-18
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| jeff_starr | user_submitted_posts | to 20260113 (inc) |
| jeff_starr | user_submitted_posts | From 20260217 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in the User Submitted Posts plugin for WordPress, in versions up to and including 20260113. It is caused by the function `usp_get_submitted_category()` accepting category IDs submitted by users via POST requests without properly validating them against the admin-configured allowed categories. This flaw allows unauthenticated attackers to assign submitted posts to arbitrary categories, including restricted ones, by crafting POST requests with manipulated category values, thereby bypassing frontend category restrictions.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability involves unauthenticated attackers sending crafted POST requests with manipulated user-submitted category IDs to assign posts to arbitrary categories, bypassing frontend restrictions.'}, {'type': 'paragraph', 'content': 'To detect exploitation attempts on your network or system, you can monitor HTTP POST requests targeting the WordPress site that include the parameter `user-submitted-category[]` or similar variations in the POST body.'}, {'type': 'paragraph', 'content': 'Suggested commands to detect such activity include:'}, {'type': 'list_item', 'content': "Using web server logs (e.g., Apache or Nginx), search for POST requests containing the suspicious parameter: `grep -i 'user-submitted-category' /var/log/apache2/access.log`"}, {'type': 'list_item', 'content': "Using network packet capture tools like tcpdump or Wireshark to filter HTTP POST requests with the parameter: `tcpdump -A -s 0 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep 'user-submitted-category'`"}, {'type': 'list_item', 'content': 'On the WordPress server, enable and review application-level logging or use security plugins that log POST submissions to detect unusual category assignments.'}, {'type': 'paragraph', 'content': 'Note that the plugin uses a nonce (`usp-nonce`) to verify legitimate submissions, so attempts without a valid nonce may be suspicious.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the User Submitted Posts plugin to the fixed version 20260217 or later, which includes sanitization and validation of submitted category IDs.
The update ensures that category IDs submitted by users are converted to integers and intersected with the allowed categories configured by the administrator, preventing unauthorized category assignments.
If updating immediately is not possible, consider temporarily disabling the plugin or restricting access to the submission functionality until the patch can be applied.
Additionally, review and tighten any web application firewall (WAF) or security plugin rules to block POST requests containing suspicious or unexpected category parameters.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing unauthorized users to assign posts to categories that should be restricted or controlled by the site administrator. This could lead to content being misclassified, potentially exposing sensitive or restricted categories to public view or disrupting the organization and integrity of your site's content.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know