CVE-2018-5213 json
The Simple Download Monitor plugin before 3.5.4 for WordPress has XSS via the sdm_upload (aka Downloadable File) parameter in an edit actio…
published 8y ago modified 4mo ago also EUVD-2018-16998
- cvss
- 5.4
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
The Simple Download Monitor plugin before 3.5.4 for WordPress has XSS via the sdm_upload (aka Downloadable File) parameter in an edit action to wp-admin/post.php.
Patch / fix
Is CVE-2018-5213 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 FencerExploit prediction
1.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/d4wner/Vulnerabilities-Report/blob/master/simple-download-monitor.md referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/Arsenal21/simple-download-monitor/issues/27 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.4 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
github.com
/Arsenal21/simple-download-monitor/commit/8ab8b9166bc87feba26a1573cf595af48eff7805
patch, third-party-advisory
-
github.com
/d4wner/Vulnerabilities-Report/blob/master/simple-download-monitor.md
exploit, third-party-advisory
-
github.com
/Arsenal21/simple-download-monitor/issues/27
exploit, third-party-advisory
-
wordpress.org
/support/topic/stored-xss-bug-at-the-latest-version-of-simple-download-monitor/
broken-link
Sources
- CVE List CVE-2018-5213
- NVD CVE-2018-5213
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.