CVE-2013-5880 json
Unspecified vulnerability in the Oracle Demantra Demand Management component in Oracle Supply Chain Products Suite 12.2.0, 12.2.1, and 12.2…
published 12y ago modified 4mo ago also EUVD-2013-5714
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 59.6%
- EPSS 59.6% chance of exploitation in 30 days, percentile 99.1%
- public exploits
- 3
- Metasploit and Exploit-DB
Summary
Unspecified vulnerability in the Oracle Demantra Demand Management component in Oracle Supply Chain Products Suite 12.2.0, 12.2.1, and 12.2.2 allows remote attackers to affect confidentiality via unknown vectors related to DM Others.
Is CVE-2013-5880 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 (EDB-39018)
- Published
Exploit prediction
59.56% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit auxiliary/scanner/http/oracle_demantra_database_credentials_leak Oracle Demantra Database Credentials Leak metasploit auxiliary, normal rank, 2014-02-28
- Metasploit auxiliary/scanner/http/oracle_demantra_file_retrieval Oracle Demantra Arbitrary File Retrieval with Authentication Bypass metasploit auxiliary, normal rank, 2014-02-28
- EDB-39018 Oracle Supply Chain Products Suite - Remote Security remote, 2014-01-14
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
References
-
oracle.com
/technetwork/topics/security/cpujan2014-1972949.html
vendor-advisory
-
osvdb.org
/102095
vdb-entry
-
securitytracker.com
/id/1029620
vdb-entry
-
secunia.com
/advisories/56474
third-party-advisory
-
securityfocus.com
/bid/64836
vdb-entry
-
securityfocus.com
/bid/64758
vdb-entry
Sources
- CVE List CVE-2013-5880
- NVD CVE-2013-5880
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.