CVE-2020-25557 json
In CMSuno 1.6.2, an attacker can inject malicious PHP code as a "username" while changing his/her username & password.
published 5y ago modified 4mo ago also EUVD-2020-18241
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 10.0%
- EPSS 10.0% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
In CMSuno 1.6.2, an attacker can inject malicious PHP code as a "username" while changing his/her username & password. After that, when attacker logs in to the application, attacker's code will be run. As a result of this vulnerability, authenticated user can run command on the server.
Is CVE-2020-25557 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-49485)
Exploit prediction
9.97% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-49485 CMSUno 1.6.2 - 'lang' Remote Code Execution (Authenticated) webapps, 2021-01-28
- fatihhcelik.blogspot.com https://fatihhcelik.blogspot.com/2020/09/cmsuno-162-remote-code-execution.html referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/161162/CMSUno-1.6.2-Remote-Code-Execution.html 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:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
fatihhcelik.blogspot.com
/2020/09/cmsuno-162-remote-code-execution.html
exploit, third-party-advisory
-
packetstormsecurity.com
/files/161162/CMSUno-1.6.2-Remote-Code-Execution.html
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2020-25557
- NVD CVE-2020-25557
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.