CVE-2020-13383 in the critical feed json
openSIS through 7.4 allows Directory Traversal.
published 6y ago modified 4mo ago also EUVD-2020-5641
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 67.8%
- EPSS 67.8% chance of exploitation in 30 days, percentile 99.3%
- public exploits
- 1
- Metasploit
Summary
openSIS through 7.4 allows Directory Traversal.
Patch / fix
Is CVE-2020-13383 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
- First public exploit (Metasploit exploit/unix/webapp/opensis_chain_exec)
- Published
Exploit prediction
67.79% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/unix/webapp/opensis_chain_exec openSIS Unauthenticated PHP Code Execution metasploit exploit, excellent rank, 2020-06-30
- packetstormsecurity.com http://packetstormsecurity.com/files/158256/openSIS-7.4-Local-File-Inclusion.html referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/158331/openSIS-7.4-Unauthenticated-PHP-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/OS4ED/openSIS-Responsive-Design/commit/1127ae0bb7c3a2883febeabc6b71ad8d73510de8
patch, third-party-advisory
-
packetstormsecurity.com
/files/158256/openSIS-7.4-Local-File-Inclusion.html
exploit, third-party-advisory, vdb-entry
-
packetstormsecurity.com
/files/158331/openSIS-7.4-Unauthenticated-PHP-Code-Execution.html
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2020-13383
- NVD CVE-2020-13383
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.