CVE-2017-1000067: SQL Injection
First published: Thu Jul 13 2017(Updated: )
MODX Revolution version 2.x - 2.5.6 is vulnerable to blind SQL injection caused by improper sanitization by the escape method resulting in authenticated user accessing database and possibly escalating privileges.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| composer/modx/revolution | >=2.0.0<=2.5.6 | 2.6.0 |
| MODX | =2.0.0 | |
| MODX | =2.0.0-rc1 | |
| MODX | =2.0.0-rc2 | |
| MODX | =2.0.0-rc3 | |
| MODX | =2.0.1 | |
| MODX | =2.1.0 | |
| MODX | =2.1.0-p12 | |
| MODX | =2.1.1 | |
| MODX | =2.1.1-p12 | |
| MODX | =2.1.2 | |
| MODX | =2.1.3 | |
| MODX | =2.1.4 | |
| MODX | =2.1.5 | |
| MODX | =2.2.0 | |
| MODX | =2.2.0-rc1 | |
| MODX | =2.2.0-rc2 | |
| MODX | =2.2.0-rc3 | |
| MODX | =2.2.1 | |
| MODX | =2.2.2 | |
| MODX | =2.2.3 | |
| MODX | =2.2.4 | |
| MODX | =2.2.5 | |
| MODX | =2.2.6 | |
| MODX | =2.2.7 | |
| MODX | =2.2.8 | |
| MODX | =2.2.9 | |
| MODX | =2.3.0 | |
| MODX | =2.3.1 | |
| MODX | =2.4.0 | |
| MODX | =2.4.1 | |
| MODX | =2.5.0 | |
| MODX | =2.5.1 | |
| MODX | =2.5.2 | |
| MODX | =2.5.3 | |
| MODX | =2.5.4 | |
| MODX | =2.5.5 | |
| MODX | =2.5.6 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-1000067?
The severity of CVE-2017-1000067 is classified as high due to potential exploitation by authenticated users to execute blind SQL injections.
How do I fix CVE-2017-1000067?
To fix CVE-2017-1000067, upgrade MODX Revolution to version 2.6.0 or later.
Which versions of MODX Revolution are affected by CVE-2017-1000067?
Versions of MODX Revolution from 2.0.0 up to 2.5.6 are affected by CVE-2017-1000067.
What type of attack is possible with CVE-2017-1000067?
CVE-2017-1000067 allows for blind SQL injection attacks that can lead to unauthorized database access and privilege escalation.
Is authentication required to exploit CVE-2017-1000067?
Yes, CVE-2017-1000067 requires an authenticated user to exploit the vulnerability.
- agent/type
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-phhm-6pgm-mxw9
- alias/CVE-2017-1000067
- agent/software-canonical-lookup
- agent/weakness
- agent/severity
- agent/references
- agent/description
- agent/author
- agent/softwarecombine
- collector/github-advisory
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/trending
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-cve
- source/NVD
- package-manager/composer
- vendor/modx
- canonical/modx
- version/modx/2.0.0
- version/modx/2.0.0-rc1
- version/modx/2.0.0-rc2
- version/modx/2.0.0-rc3
- version/modx/2.0.1
- version/modx/2.1.0
- version/modx/2.1.0-p12
- version/modx/2.1.1
- version/modx/2.1.1-p12
- version/modx/2.1.2
- version/modx/2.1.3
- version/modx/2.1.4
- version/modx/2.1.5
- version/modx/2.2.0
- version/modx/2.2.0-rc1
- version/modx/2.2.0-rc2
- version/modx/2.2.0-rc3
- version/modx/2.2.1
- version/modx/2.2.2
- version/modx/2.2.3
- version/modx/2.2.4
- version/modx/2.2.5
- version/modx/2.2.6
- version/modx/2.2.7
- version/modx/2.2.8
- version/modx/2.2.9
- version/modx/2.3.0
- version/modx/2.3.1
- version/modx/2.4.0
- version/modx/2.4.1
- version/modx/2.5.0
- version/modx/2.5.1
- version/modx/2.5.2
- version/modx/2.5.3
- version/modx/2.5.4
- version/modx/2.5.5
- version/modx/2.5.6