| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.8 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in phpRPG 0.8. This affects an unknown part of the file index.php. The manipulation of the argument Username leads to sql injection. This vulnerability is listed as CVE-2007-6469. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in phpRPG 0.8 and classified as very critical. This issue affects an unknown code of the file index.php. The manipulation of the argument username with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in index.php in phpRPG 0.8, when magic_qutoes_gpc is disabled, allows remote attackers to execute arbitrary SQL commands via the username parameter. NOTE: some of these details are obtained from third party information.
The weakness was presented 12/19/2007 by Michael Brooks (Website). It is possible to read the advisory at marc.info. The identification of this vulnerability is CVE-2007-6469 since 12/19/2007. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/13/2018). The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
By approaching the search of inurl:index.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at SecurityFocus (BID 26884†) and Secunia (SA27968†). See VDB-40186 and VDB-40164 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.8
VulDB Base Score: 9.8
VulDB Temp Score: 9.8
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
Google Hack: 🔍
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
12/15/2007 🔍12/17/2007 🔍
12/19/2007 🔍
12/19/2007 🔍
12/19/2007 🔍
03/16/2015 🔍
09/13/2018 🔍
Sources
Advisory: marc.infoResearcher: Michael Brooks
Status: Not defined
CVE: CVE-2007-6469 (🔍)
GCVE (CVE): GCVE-0-2007-6469
GCVE (VulDB): GCVE-100-40163
SecurityFocus: 26884 - phpRPG Multiple Vulnerabilities
Secunia: 27968 - phpRPG SQL Injection and Information Disclosure, Moderately Critical
See also: 🔍
Entry
Created: 03/16/2015 13:43Updated: 09/13/2018 09:37
Changes: 03/16/2015 13:43 (49), 09/13/2018 09:37 (7)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.