CVE-2020-4041: The filename of uploaded files vulnerable to stored XSS
Impact
The filename of uploaded files was vulnerable to stored XSS. It is not possible to inject javascript code in the file name when creating/uploading the file. But, once created/uploaded, it can be renamed to inject the payload in it.
Additionally, the measures to prevent renaming the file to disallowed filename extensions could be circumvented.
Patches
This is fixed in Bolt 3.7.1.
References
Related issue: https://github.com/bolt/bolt/pull/7853
Other sources
In Bolt CMS before version 3.7.1, the filename of uploaded files was vulnerable to stored XSS. It is not possible to inject javascript code in the file name when creating/uploading the file. But, once created/uploaded, it can be renamed to inject the payload in it. Additionally, the measures to prevent renaming the file to disallowed filename extensions could be circumvented. This is fixed in Bolt 3.7.1.
— MITRE
The filename of uploaded files vulnerable to stored XSS
— Packagist
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/bolt/boltto a version that resolves this vulnerability.Fixed in 3.7.1 - Upgrade
Upgrade
Bolt CMSto a version that resolves this vulnerability.Fixed in 3.7.1
Event History
Frequently Asked Questions
What is the severity of CVE-2020-4041?
CVE-2020-4041 is considered a medium severity vulnerability due to its potential for stored XSS attacks.
How do I fix CVE-2020-4041?
To fix CVE-2020-4041, upgrade Bolt CMS to version 3.7.1 or higher.
What kind of attack can CVE-2020-4041 be used for?
CVE-2020-4041 can be exploited for stored XSS attacks through renaming uploaded files.
Which versions of Bolt CMS are affected by CVE-2020-4041?
CVE-2020-4041 affects all versions of Bolt CMS prior to 3.7.1.
Is it possible to execute JavaScript code through file uploads due to CVE-2020-4041?
Yes, CVE-2020-4041 allows for the execution of JavaScript code by renaming uploaded files.