| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in MODX Evolution up to 1.0.4. It has been rated as critical. This vulnerability affects unknown code. Performing a manipulation results in sql injection. This vulnerability is identified as CVE-2010-3929. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in MODX Evolution up to 1.0.4 (Content Management System). It has been classified as critical. This affects an unknown function. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in MODx Evolution 1.0.4 and earlier allows remote attackers to execute arbitrary SQL commands via unknown vectors related to AjaxSearch.
The weakness was released 01/26/2011 (Website). The advisory is shared at jvn.jp. This vulnerability is uniquely identified as CVE-2010-3929 since 10/12/2010. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
A possible mitigation has been published even before and not after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (65082), SecurityFocus (BID 46163†), OSVDB (70771†) and Vulnerability Center (SBV-29902†). Entries connected to this vulnerability are available at VDB-56309 and VDB-56302. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://modx.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/12/2010 🔍01/19/2011 🔍
01/19/2011 🔍
01/19/2011 🔍
01/26/2011 🔍
02/01/2011 🔍
02/04/2011 🔍
02/22/2011 🔍
03/20/2015 🔍
04/17/2018 🔍
Sources
Vendor: modx.comAdvisory: jvn.jp
Status: Not defined
Confirmation: 🔍
CVE: CVE-2010-3929 (🔍)
GCVE (CVE): GCVE-0-2010-3929
GCVE (VulDB): GCVE-100-56301
X-Force: 65082
SecurityFocus: 46163 - MODx Evolution Directory Traversal and SQL Injection Vulnerabilities
OSVDB: 70771 - MODx Evolution AjaxSearch Unspecified SQL Injection
Vulnerability Center: 29902 - MODx Evolution 1.0.4 and Prior Remote SQL Injection Vulnerability via Vectors Related to AjaxSearch, High
See also: 🔍
Entry
Created: 03/20/2015 16:16Updated: 04/17/2018 10:36
Changes: 03/20/2015 16:16 (51), 04/17/2018 10:36 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.