CVE Intelligence
Skip to main content
CRITICAL

CVE-2023-45603

CVE-2023-45603 — WordPress User Submitted Posts Plugin <= 20230902 is vulnerable to Arbitrary File Upload

Unrestricted Upload of File with Dangerous Type vulnerability in Jeff Starr User Submitted Posts – Enable Users to Submit Posts from the Front End.This issue affects User Submitted Posts – Enable Users to Submit Posts from the Front End: from n/a through 20230902.

Published Updated Sources: cvelistV5, Patchstack

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

1%

chance of exploitation in 30 days

Affects

jeff starr

user_submitted_posts_enable_users_to_submit_posts_from_the_front_end

CVSS base

9

CRITICAL

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

jeff starr

Products (1)

user submitted posts enable users to submit posts from the front end

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
9CVSS 3.1CRITICAL——cvelistV5

Weakness & attack patterns

  • CWE-434

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1574.010Hijack Execution Flow: ServicesFile Permissions Weakness

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /a.

References

1 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.