The user-submitted-posts plugin before 20160215 for WordPress has XSS via the user-submitted-content field.

published 2019-09-20 7y ago modified 2026-06-17 4mo ago also EUVD-2016-1992

cvss: 6.1; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.2%; EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits: 0; none known

Patch / fix

fixed in 1

plugin-planet user_submitted_posts 20160215

Is CVE-2016-11001 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.18% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

securityfocus.com https://www.securityfocus.com/archive/1/537616/30/0/threaded referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	6.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:P/A:N

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

Technology feeds

WordPress rss critical rss

References

securityfocus.com /archive/1/537616/30/0/threaded
exploit, third-party-advisory, vdb-entry
wordpress.org /plugins/user-submitted-posts/#developers
product, third-party-advisory

Sources

CVE List CVE-2016-11001
NVD CVE-2016-11001

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.