Quick answers
- Is CVE-2017-5517 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2017-5517 being exploited in the wild.
- How severe is CVE-2017-5517?
- Critical severity, with a CVSS score of 9.8, published 17 January 2017.
- Which products and versions are affected?
- GeniXCMS GeniXCMS through 0.0.8.
- Is there a fix for CVE-2017-5517?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2017-5517 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2017-5517?
- Check whether you run Metalgenix Genixcms. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A SQL injection vulnerability exists in GeniXCMS versions up to and including 0.0.8 within the 'author.control.php' file. The vulnerability is caused by improper neutralization of special elements used in an SQL command, specifically affecting the 'type' parameter. A remote, unauthenticated attacker can exploit this by sending a specially crafted network request to execute arbitrary SQL commands against the backend database. Successful exploitation could result in full data exfiltration, modification of database records, or administrative bypass. A patch was reportedly addressed in the project's issue tracker.
Affected products
- GeniXCMS GeniXCMS through 0.0.8
Timeline
- 2017-01-17: disclosed
- 2017-01-17: advisory