User Submitted Posts at a glance
- 15 publicly disclosed vulnerabilities, 7 of them rated High or Critical. The most recent was disclosed on Oct 30, 2026.
- Ranked #1540 by popularity on WordPress.org (10,000+ active installs).
- The latest version is 20261029 (released Oct 29, 2026). The most recent security fix shipped in 20261029.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your User Submitted Posts version
Enter the User Submitted Posts version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “User Submitted Posts”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “User Submitted Posts”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (20261029). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known User Submitted Posts vulnerabilities
User Submitted Posts <= 20260916 - Unauthenticated Stored DOM-Based Cross-Site Scripting via 'user-submitted-content' Parameter via Block-Comment Shortcode Splitting
Cross-site scripting (XSS) · CVE-2026-119162
Affected versions: ≤ 20260916
Fixed in: 20261029
Severity: High 7.2 · Disclosed Oct 30, 2026
User Submitted Posts – Enable Users to Submit Posts from the Front End <= 20260810 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-62084
Affected versions: ≤ 20260810
Fixed in: 20260916
Severity: Medium 6.4 · Disclosed Sep 30, 2026
User Submitted Posts <= 20260607 - Unauthenticated Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-11570
Affected versions: ≤ 20260607
Fixed in: 20260608
Severity: High 7.2 · Disclosed Jun 10, 2026
User Submitted Posts <= 20260113 - Incorrect Authorization to Unauthenticated Category Restriction Bypass via 'user-submitted-category' Parameter
Other weakness · CVE-2026-2126
Affected versions: ≤ 20260113
Fixed in: 20260217
Severity: Medium 5.3 · Disclosed Feb 17, 2026
User Submitted Posts – Enable Users to Submit Posts from the Front End <= 20251210 - Unauthenticated Stored Cross-Site Scripting via Custom Field
Cross-site scripting (XSS) · CVE-2026-0800
Affected versions: ≤ 20251210
Fixed in: 20260110
Severity: High 7.2 · Disclosed Jan 23, 2026
User Submitted Posts <= 20260110 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'usp_access' Shortcode
Cross-site scripting (XSS) · CVE-2026-0913
Affected versions: ≤ 20260110
Fixed in: 20260113
Severity: Medium 6.4 · Disclosed Jan 15, 2026
User Submitted Posts <= 20251121 - Unauthenticated Open Redirect
Open redirect · CVE-2025-68509
Affected versions: ≤ 20251121
Fixed in: 20251210
Severity: Medium 5.3 · Disclosed Jan 1, 2026
User Submitted Posts <= 20241026 - Authenticated (Admin+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2025-2874
Affected versions: ≤ 20241026
Fixed in: 20250327
Severity: Medium 4.4 · Disclosed Apr 2, 2025
User Submitted Posts – Enable Users to Submit Posts from the Front End <= 20240319 - Authenticated (Admin+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2024-5002
Affected versions: ≤ 20240319
Fixed in: 20240516
Severity: Medium 4.4 · Disclosed Jun 22, 2024
User Submitted Posts <= 20230902 - Unauthenticated Arbitrary File Upload
Arbitrary file upload · CVE-2023-45603
Affected versions: ≤ 20230902
Fixed in: 20230914
Severity: Critical 9.8 · Disclosed Oct 10, 2023
User Submitted Posts <= 20230901 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
Cross-site scripting (XSS) · CVE-2023-7251
Affected versions: ≤ 20230901
Fixed in: 20230902
Severity: Medium 6.4 · Disclosed Sep 6, 2023
User Submitted Posts – Enable Users to Submit Posts from the Front End <= 20230811 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
Cross-site scripting (XSS) · CVE-2023-4779
Affected versions: ≤ 20230811
Fixed in: 20230901
Severity: Medium 6.4 · Disclosed Sep 5, 2023
User Submitted Posts <= 20230809 - Unauthenticated Stored Cross-Site Scripting via 'user-submitted-content'
Cross-site scripting (XSS) · CVE-2023-4308
Affected versions: ≤ 20230809
Fixed in: 20230811
Severity: High 7.2 · Disclosed Aug 14, 2023
User Submitted Posts <= 20190312 - Unauthenticated Arbitrary File Upload
Arbitrary file upload · CVE-2019-25138
Affected versions: < 20190426
Fixed in: 20190426
Severity: Critical 9.8 · Disclosed May 2, 2019
User Submitted Posts < 20160215 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2016-11001
Affected versions: < 20160215
Fixed in: 20160215
Severity: High 7.2 · Disclosed Feb 10, 2016
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| User Submitted Posts <= 20260916 - Unauthenticated Stored DOM-Based Cross-Site Scripting via 'user-submitted-content' Parameter via Block-Comment Shortcode SplittingCross-site scripting (XSS) · CVE-2026-119162 | ≤ 20260916 | 20261029 | High 7.2 | Oct 30, 2026 |
| User Submitted Posts – Enable Users to Submit Posts from the Front End <= 20260810 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-62084 | ≤ 20260810 | 20260916 | Medium 6.4 | Sep 30, 2026 |
| User Submitted Posts <= 20260607 - Unauthenticated Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-11570 | ≤ 20260607 | 20260608 | High 7.2 | Jun 10, 2026 |
| User Submitted Posts <= 20260113 - Incorrect Authorization to Unauthenticated Category Restriction Bypass via 'user-submitted-category' ParameterOther weakness · CVE-2026-2126 | ≤ 20260113 | 20260217 | Medium 5.3 | Feb 17, 2026 |
| User Submitted Posts – Enable Users to Submit Posts from the Front End <= 20251210 - Unauthenticated Stored Cross-Site Scripting via Custom FieldCross-site scripting (XSS) · CVE-2026-0800 | ≤ 20251210 | 20260110 | High 7.2 | Jan 23, 2026 |
| User Submitted Posts <= 20260110 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'usp_access' ShortcodeCross-site scripting (XSS) · CVE-2026-0913 | ≤ 20260110 | 20260113 | Medium 6.4 | Jan 15, 2026 |
| User Submitted Posts <= 20251121 - Unauthenticated Open RedirectOpen redirect · CVE-2025-68509 | ≤ 20251121 | 20251210 | Medium 5.3 | Jan 1, 2026 |
| User Submitted Posts <= 20241026 - Authenticated (Admin+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2025-2874 | ≤ 20241026 | 20250327 | Medium 4.4 | Apr 2, 2025 |
| User Submitted Posts – Enable Users to Submit Posts from the Front End <= 20240319 - Authenticated (Admin+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2024-5002 | ≤ 20240319 | 20240516 | Medium 4.4 | Jun 22, 2024 |
| User Submitted Posts <= 20230902 - Unauthenticated Arbitrary File UploadArbitrary file upload · CVE-2023-45603 | ≤ 20230902 | 20230914 | Critical 9.8 | Oct 10, 2023 |
| User Submitted Posts <= 20230901 - Authenticated (Contributor+) Stored Cross-Site Scripting via ShortcodeCross-site scripting (XSS) · CVE-2023-7251 | ≤ 20230901 | 20230902 | Medium 6.4 | Sep 6, 2023 |
| User Submitted Posts – Enable Users to Submit Posts from the Front End <= 20230811 - Authenticated (Contributor+) Stored Cross-Site Scripting via ShortcodeCross-site scripting (XSS) · CVE-2023-4779 | ≤ 20230811 | 20230901 | Medium 6.4 | Sep 5, 2023 |
| User Submitted Posts <= 20230809 - Unauthenticated Stored Cross-Site Scripting via 'user-submitted-content'Cross-site scripting (XSS) · CVE-2023-4308 | ≤ 20230809 | 20230811 | High 7.2 | Aug 14, 2023 |
| User Submitted Posts <= 20190312 - Unauthenticated Arbitrary File UploadArbitrary file upload · CVE-2019-25138 | < 20190426 | 20190426 | Critical 9.8 | May 2, 2019 |
| User Submitted Posts < 20160215 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2016-11001 | < 20160215 | 20160215 | High 7.2 | Feb 10, 2016 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 30, 2026.
Most common weaknesses in User Submitted Posts
Cross-site scripting (XSS)
11 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Arbitrary file upload
2 issues
An attacker can upload a malicious file disguised as an image or document. Once it is on the server, it can be used to take over the site.
Open redirect
1 issue
Links on your own domain can be used to send people to a fake site, which makes phishing emails look more convincing.
Frequently asked questions
Is User Submitted Posts safe to use?
User Submitted Posts is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (20261029) and turn on automatic updates.
How do I find which version of User Submitted Posts my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesUser Submitted Posts on WordPress.org