CVE-2022-3921 in the critical feed json
Listingo < 3.2.7 - Unauthenticated Arbitrary File Upload
published 3y ago modified 4mo ago also EUVD-2022-43255
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 21.2%
- EPSS 21.2% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
The Listingo WordPress theme before 3.2.7 does not validate files to be uploaded via an AJAX action available to unauthenticated users, which could allow them to upload arbitrary files and lead to RCE
Patch / fix
- Unknown Listingo 3.2.7
Is CVE-2022-3921 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 FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
21.21% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/e39b59b0-f24f-4de5-a21c-c4de34c3a14f referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Unknown Listingo
Classification
- Technology feeds
References
-
wpscan.com
/vulnerability/e39b59b0-f24f-4de5-a21c-c4de34c3a14f
exploit, vdb-entry, technical-description, third-party-advisory
Sources
- CVE List CVE-2022-3921
- NVD CVE-2022-3921
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.