How severe is CVE-2017-5346?

CVE-2017-5346 has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-5346?

CVE-2017-5346 affects the following packages: genix/cms (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2017-5346?

Update genix/cms to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-5346 is resolved across your whole dependency graph.

How do I detect CVE-2017-5346 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for genix/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-5346 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2017-5346 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2017-5346, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-5346?

CVE-2017-5346 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 77th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2017-5346?

CVE-2017-5346 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2017-5346 published, and has it been updated?

CVE-2017-5346 was published on January 12, 2017 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

CVE-2017-5346 — cms

HIGHFix: semplon/GeniXCMS@abfbb61

CVE-2017-5346 is a high-severity (CVSS 7.2) SQL Injection vulnerability in genix/cms. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for genix/cms — see the affected versions and patch details below.

GeniXCMS SQL injection vulnerability

Also known asGHSA-2ppw-6xvg-rwgw

Published

Jan 12, 2017

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘genix/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

SQL injection vulnerability in inc/lib/Control/Backend/posts.control.php in GeniXCMS 0.0.8 allows remote authenticated administrators to execute arbitrary SQL commands via the id parameter to gxadmin/index.php.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`genix/cms`	all versions	1.0.0`composer require genix/cms:^1.0.0`

Affected Products

1 product · 1 configurations

Application

genixcmsgenixcms

1 version

0.0.8

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

SQL injection vulnerability in inc/lib/Control/Backend/posts.control.php…

github.comNVDMar 2019

Report on code610.blogspot.com

code610.blogspot.comNVDMar 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for genix/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update genix/cms to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-5346 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-5346 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.2/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-89SQL Injection

Weaponization

No Nuclei template or Metasploit module yet. 2 public proof-of-concept references are listed on this page.

Timeline

Disclosed

Jan 12, 2017

First exploit

Mar 15, 2019

Last updated

Oct 20, 2026

Identifiers

CVE-2017-5346

GHSA-2ppw-6xvg-rwgw

References

Advisorysecurityfocus.com Advisorynvd.nist.gov · CVE 2017 5346 Fixgithub.com Webgithub.com · abfbb6103bfa860275f89d1215ed9c3cba94791e Packagegithub.com · GeniXCMS Evidencecode610.blogspot.com · genixcms sql injection quick autopsy

Related vulnerabilities

This CVE is high severity; 3 of 8 other CVEs affecting genix/cms are rated as high or higher (top: high).

CVE-2017-14231CVE-2017-8377CVE-2017-14765CVE-2017-8762CVE-2017-8376CVE-2017-14764CVE-2017-8780CVE-2016-10096

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2017-5346 — cms

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2017-5346 in your dependencies?