CVE-2013-5106 json
A Code Execution vulnerability exists in select.py when using python-mode 2012-12-19.
published 6y ago modified 4mo ago also EUVD-2013-4947
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
A Code Execution vulnerability exists in select.py when using python-mode 2012-12-19.
Is CVE-2013-5106 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.72% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com http://github.com/klen/python-mode/issues/162 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
github.com
/klen/python-mode/issues/162
exploit, issue-tracking, third-party-advisory
Sources
- CVE List CVE-2013-5106
- NVD CVE-2013-5106
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.