# CVE-2017-5519: GeniXCMS SQL injection in Posts.class.php

Source: https://junglewise.ai/threats/cve-2017-5519-genixcms-sql-injection-in-posts-class-php  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2017-01-17. Updated: 2026-05-13  
License: CC BY 4.0 with a link back

CVE-2017-5519 · Severity: critical · CVSS 9.8 · Published 2017-01-17

GeniXCMS, a content management system used for building and managing websites, contains a critical security flaw. An attacker can use this vulnerability to gain unauthorized access to the website's database, potentially leading to the theft of sensitive user data, modification of site content, or complete takeover of the application. This issue can be exploited remotely without requiring any login credentials.

Technologies: [Metalgenix Genixcms](https://junglewise.ai/threats/technologies/genixcms). Vendors: [Metalgenix](https://junglewise.ai/threats/vendors/metalgenix).

## Quick answers

**Is CVE-2017-5519 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2017-5519 being exploited in the wild.

**How severe is CVE-2017-5519?** 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-5519?** 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-5519 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2017-5519?** 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 Posts.class.php component. The flaw is caused by insufficient sanitization of the 'id' parameter, allowing an unauthenticated remote attacker to inject and execute arbitrary SQL commands. By exploiting this vulnerability, an attacker can bypass authentication, extract sensitive information from the database, modify or delete data, and in some configurations, achieve remote code execution on the underlying server. A patch was reportedly addressed in subsequent updates following the disclosure on GitHub.

## Affected products

- GeniXCMS GeniXCMS through 0.0.8

## Timeline

- 2017-01-17: disclosed
- 2017-01-17: advisory

## References

- [http://www.securityfocus.com/bid/95458](http://www.securityfocus.com/bid/95458)
- [https://github.com/semplon/GeniXCMS/issues/67](https://github.com/semplon/GeniXCMS/issues/67)

## Related threats

- [GeniXCMS SQL injection in Options.class.php](https://junglewise.ai/threats/cve-2017-5575-genixcms-sql-injection-in-options-class-php)
- [GeniXCMS SQL injection in register.php](https://junglewise.ai/threats/cve-2017-5574-genixcms-sql-injection-in-register-php)
- [GeniXCMS unrestricted file upload in media rename feature](https://junglewise.ai/threats/cve-2017-5520-genixcms-unrestricted-file-upload-in-media-rename-feature)
- [GeniXCMS SSRF in media-file upload feature](https://junglewise.ai/threats/cve-2017-5518-genixcms-ssrf-in-media-file-upload-feature)
- [GeniXCMS SQL injection in author.control.php](https://junglewise.ai/threats/cve-2017-5517-genixcms-sql-injection-in-author-control-php)