User Submitted Posts <= 20260916 - Unauthenticated Stored DOM-Based Cross-Site Scripting via 'user-submitted-content' Parameter via Block-Comment Shortcode Splitting
Strategic Overview
- Status
- Patched in 20261029
- Affected Version
<= 20260916- CVSS
- 7.2High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation
- CVE
CVE-2026-119162
At a glance
CVE-2026-119162 is a high-severity Improper Neutralization of Input During Web Page Generation vulnerability in the User Submitted Posts WordPress plugin, affecting versions <= 20260916. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 20261029; sites on affected versions should update now. Disclosed October 2026, reported by UKO.
Vulnerability Overview
The User Submitted Posts – Enable Users to Submit Posts from the Front End plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'user-submitted-content' parameter in all versions up to, and including, 20260916 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. On a default installation the submitted post is held as Pending and requires admin approval before the payload is reachable by other visitors; however, if the plugin's "publish immediately" option is enabled, no approval step exists and the stored payload becomes live without any moderator interaction.
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 privileges on the target site, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation
User Submitted Posts <= 20260916 carries this weakness at user-submitted-content, and reaching it takes no account at all. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For User Submitted Posts the fix is 20261029: builds <= 20260916 are affected, anything from 20261029 onward is not.
Remediation
Update to version 20261029, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: User Submitted Posts 20261029 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in User Submitted Posts – Enable Users to Submit Posts from the Front End
- 9.8CVE-2023-45603: User Submitted Posts <= 20230902 Arbitrary File Upload
CVE-2023-45603 - 9.8CVE-2019-25138: User Submitted Posts <= 20190312 Arbitrary File Upload
CVE-2019-25138 - 6.4CVE-2026-62084: User Submitted Posts Stored XSS
CVE-2026-62084 - 6.4CVE-2026-0913: User Submitted Posts <= 20260110 Stored XSS
CVE-2026-0913 - 6.4CVE-2023-7251: User Submitted Posts <= 20230901 Stored XSS
CVE-2023-7251 - 6.4CVE-2023-4779: User Submitted Posts Stored XSS
CVE-2023-4779 - 5.3CVE-2026-2126: User Submitted Posts Incorrect Authorization
CVE-2026-2126 - 5.3CVE-2025-68509: User Submitted Posts <= 20251121 Open Redirect
CVE-2025-68509
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C