CVE-2015-5457 json
PivotX before 2.3.11 does not validate the new file extension when renaming a file with multiple extensions, which allows remote attackers…
published 11y ago modified 4mo ago also EUVD-2015-5413
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.6%
- EPSS 4.6% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
PivotX before 2.3.11 does not validate the new file extension when renaming a file with multiple extensions, which allows remote attackers to execute arbitrary code by uploading a crafted file, as demonstrated by a file named foo.php.php.
Is CVE-2015-5457 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
4.65% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- software-talk.org http://software-talk.org/blog/2015/06/session-fixation-xss-code-execution-vulnerability-pivotx/ referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/132474/PivotX-2.3.10-Session-Fixation-XSS-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
software-talk.org
/blog/2015/06/session-fixation-xss-code-execution-vulnerability-pivotx/
exploit
-
packetstormsecurity.com
/files/132474/PivotX-2.3.10-Session-Fixation-XSS-Code-Execution.html
exploit
- blog.pivotx.net /archive/2015/06/21/pivotx-2311-released
-
securityfocus.com
/bid/75577
vdb-entry
-
securityfocus.com
/archive/1/535860/100/0/threaded
mailing-list
- sourceforge.net /p/pivot-weblog/code/4452/tree//branches/2.3.x/pivotx/fileupload.php?diff=51a4cb5e34309d75c0d1612a:4451
Sources
- CVE List CVE-2015-5457
- NVD CVE-2015-5457
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.