CVE-2019-12744 in the critical feed json
SeedDMS before 5.1.11 allows Remote Command Execution (RCE) because of unvalidated file upload of PHP scripts, a different vulnerability th…
published 7y ago modified 4mo ago also EUVD-2019-4332
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.5%
- EPSS 11.5% chance of exploitation in 30 days, percentile 96%
- public exploits
- 2
- Exploit-DB
Summary
SeedDMS before 5.1.11 allows Remote Command Execution (RCE) because of unvalidated file upload of PHP scripts, a different vulnerability than CVE-2018-12940.
Patch / fix
- seeddms seeddms 5.1.11
Is CVE-2019-12744 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 FencerTimeline
- Published
- First public exploit (EDB-47022)
Exploit prediction
11.49% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-50062 Seeddms 5.1.10 - Remote Command Execution (RCE) (Authenticated) webapps, 2021-06-25
- EDB-47022 SeedDMS versions < 5.1.11 - Remote Command Execution webapps, 2019-06-24
- secfolks.blogspot.com https://secfolks.blogspot.com/2019/06/exploit-for-cve-2019-12744-remote.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
secfolks.blogspot.com
/2019/06/exploit-for-cve-2019-12744-remote.html
exploit, third-party-advisory
-
sourceforge.net
/p/seeddms/code/ci/master/tree/CHANGELOG
release-notes, third-party-advisory
- packetstormsecurity.com /files/153383/SeedDMS-Remote-Command-Execution.html
- packetstormsecurity.com /files/163283/Seeddms-5.1.10-Remote-Command-Execution.html
Sources
- CVE List CVE-2019-12744
- NVD CVE-2019-12744
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.