Earcms develops a narrowly scoped music management and audio content platform centered on its EAR product line, where the observed vulnerability pattern centers on improper file-upload handling. The recurring signal reflects a straightforward input-validation weakness endemic to web applications that accept user-supplied media files; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Earcms over time
Signals from CVEs in this vendor scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-18912CRITICAL An issue found in Earcms Ear App v.20181124 allows a remote attacker to execute arbitrary code via the uload/index-uplog.php. | Aug 29, 2023 | 9.8 | 29 | NO | NO |
CVE-2017-11756HIGH In Earcms Ear Music through 4.1 build 20170710, remote authenticated users can execute arbitrary PHP code by changing the allowable music-upload extensions to include .php in addit | Jul 30, 2017 | 7.0 | 18 | NO | NO |
Signals from CVEs in this vendor scope (2 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Earcms.
Media articles that mention a CVE ID that affects a product developed by Earcms — matched by CVE ID, not by vendor name.