Spiffyjr phpRaid 3.0.6 Authorization register.php sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Spiffyjr phpRaid 3.0.6. The impacted element is an unknown function of the file register.php of the component Authorization. This manipulation causes sql injection. This vulnerability appears as CVE-2006-3318. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in Spiffyjr phpRaid 3.0.6. It has been declared as critical. Affected by this vulnerability is some unknown processing of the file register.php of the component Authorization. The manipulation with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in register.php for phpRaid 3.0.6 and possibly other versions, when the authorization type is phpraid, allows remote attackers to execute arbitrary SQL commands via the (1) username and (2) email parameters.
The weakness was presented 06/29/2006 (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2006-3318 since 06/29/2006. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
It is declared as proof-of-concept. By approaching the search of inurl:register.php it is possible to find vulnerable targets with Google Hacking.
The vulnerability is also documented in the databases at X-Force (27459) and Secunia (SA20865†). See VDB-31103, VDB-31092 and VDB-84198 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
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: Proof-of-Concept
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
06/29/2006 🔍06/29/2006 🔍
06/29/2006 🔍
06/29/2006 🔍
03/12/2015 🔍
07/30/2018 🔍
Sources
Advisory: securityfocus.com⛔Status: Confirmed
CVE: CVE-2006-3318 (🔍)
GCVE (CVE): GCVE-0-2006-3318
GCVE (VulDB): GCVE-100-31093
X-Force: 27459 - phpRaid register.php SQL injection
Secunia: 20865 - phpRaid SQL Injection and File Inclusion Vulnerabilities, Highly Critical
Vupen: ADV-2006-2593
See also: 🔍
Entry
Created: 03/12/2015 14:25Updated: 07/30/2018 08:00
Changes: 03/12/2015 14:25 (51), 07/30/2018 08:00 (5)
Complete: 🔍
Cache ID: 216:754: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.