CVE-2019-17575
First published: Mon Oct 14 2019(Updated: )
A file-rename filter bypass exists in admin/media/rename.php in WBCE CMS 1.4.0 and earlier. This can be exploited by an authenticated user with admin privileges to rename a media filename and extension. (For example: place PHP code in a .jpg file, and then change the file's base name to filename.ph and change the file's extension to p. Because of concatenation, the name is then treated as filename.php.) At the result, remote attackers can execute arbitrary PHP code.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Wbce Wbce Cms | <=1.4.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID for this issue?
The vulnerability ID for this issue is CVE-2019-17575.
What is the severity of CVE-2019-17575?
The severity of CVE-2019-17575 is high, with a severity value of 7.2.
Which versions of WBCE CMS are affected by CVE-2019-17575?
WBCE CMS 1.4.0 and earlier versions are affected by CVE-2019-17575.
How can an authenticated user with admin privileges exploit CVE-2019-17575?
An authenticated user with admin privileges can exploit CVE-2019-17575 by renaming a media filename and extension, allowing arbitrary file upload.
Is there a fix available for CVE-2019-17575?
Yes, a fix is available for CVE-2019-17575. It is recommended to update to a version of WBCE CMS that is not affected by the vulnerability.
- collector/nvd-index
- agent/weakness
- agent/type
- vendor/wbce
- canonical/wbce wbce cms
- version/wbce wbce cms/1.4.0