Live › vulnerability › CVE-2026-119162
The User Submitted Posts WordPress plugin fails to sanitize the 'user-submitted-content' parameter, letting unauthenticated visitors store scripts that run in other users' browsers. By default submissions wait for admin approval, but with the 'publish immediately' option enabled the payload goes live without review.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-31 07:34 UTC. All times on this page are UTC.
Sites running the User Submitted Posts plugin at version 20260916 or earlier. The risk is highest where the 'publish immediately' option is enabled, since submissions then skip moderation; with default settings, submissions are held as Pending until an admin approves them.
No product ranges from the sources yet.
20260916 are implied as fixed by the advisory's range; the exact fixed version is unknownEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-119162")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.