CVE-2017-15683: XML injection in Crafter CMS
Summary
CVE-2017-15683: XML injection in Crafter CMS. Affects org.craftercms:crafter-core versions >= 3.0.0, < 3.0.1. Fixed in 3.0.1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Crafter CMS is an open-source content management system that allows users to create and manage websites. It includes a component called Crafter Studio, which provides a web-based interface for site creation and management. The vulnerability affects Crafter Studio version 3.0 prior to 3.0.1. This version of Crafter Studio allows unauthenticated attackers to create a site with specially crafted XML, which can be used to retrieve operating system files out-of-band.
Vulnerability Detail
The vulnerability in Crafter CMS Crafter Studio 3.0 allows an attacker to exploit XML injection. By creating a site with specially crafted XML, an attacker can manipulate the XML parsing process and retrieve operating system files. This can lead to unauthorized access to sensitive information or the execution of arbitrary code. The vulnerability has a CVSS score of 8.6, indicating a high severity level.
How To Fix
Minimum fixed version
3.0.1
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
The XML injection vulnerability in Crafter CMS Crafter Studio 3.0 prior to 3.0.1 allows unauthenticated attackers to retrieve operating system files. To mitigate this vulnerability, users should upgrade to Crafter Studio version 3.0.1 or later. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.craftercms:crafter-core →
FAQ
The vulnerability allows an attacker to retrieve operating system files, potentially leading to unauthorized access to sensitive information or the execution of arbitrary code.
No, the vulnerability can be exploited by an unauthenticated attacker.
There are no known instances of this vulnerability being exploited in the wild.
No, access controls alone cannot mitigate this vulnerability. The recommended solution is to upgrade to the patched version of Crafter Studio.
No, there is no known workaround for this vulnerability. Upgrading to the patched version is the recommended solution.
References
Related vulnerabilities
Recent vulnerabilities recorded for org.craftercms:crafter-core.
