NVD / CVE Program· CNA Wordfence

CVE-2019-25138: User Submitted Posts <= 20190312 - Unauthenticated Arbitrary File Upload

Noroxi assessment

Priority: Plan (action score 40/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 2.3% (FIRST EPSS); higher than 83.4% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: specialk User Submitted Posts – Enable Users to Submit Posts from the Front End 20190426.

Add it to your regular patch cycle. Upgrade to specialk User Submitted Posts – Enable Users to Submit Posts from the Front End 20190426 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The User Submitted Posts plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the usp_check_images function in versions up to, and including, 20190312. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected sites server which may make remote code execution possible.

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Published: Jun 6, 2023
Updated: Jun 16, 2026
EPSS: 2.3% · 83th percentile
CWE: CWE-434

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 2.3%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 9.8
CNA · Wordfence: 9.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Is User Submitted Posts – Enable Users to Submit Posts from the Front End on your site?

WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
plugin-planet	user submitted posts	cpe:2.3:a:plugin-planet:user_submitted_posts

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

plugin-planet user submitted postsup to 20190312 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Wordfence). Independent of NVD's CPE analysis and usually ahead of it.

specialk User Submitted Posts – Enable Users to Submit Posts from the Front End
- before 20190426affected · semver

Same product

plugin-planet: all records

Other highest-scoring records for the same primary product.

CVE-2023-45603WordPress User Submitted Posts Plugin <= 20230902 is vulnerable to Arbitrary File Upload
39Monitor
CVE-2016-11001The user-submitted-posts plugin before 20160215 for WordPress has XSS via the user-submitted-content field.
24Monitor
CVE-2023-4779User Submitted Posts – Enable Users to Submit Posts from the Front End <= 20230811 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
21Monitor

Published before and after this one in the same product

Later →CVE-2023-4308Aug 15, 2023 · User Submitted Posts <= 20230809 - Unauthenticated Stored Cross-Site Scripting via 'user-submitted-content'
21Monitor
Later →CVE-2024-5002Jul 13, 2024 · User Submitted Posts < 20240516 - Admin+ Stored XSS
19Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
specialk User Submitted Posts – Enable Users to Submit Posts from the Front End	20190426	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Jerome Bruandetfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).