Simple PHP Forum up to 0.3 logon_user.php Username sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Simple PHP Forum up to 0.3. Affected by this vulnerability is an unknown functionality of the file logon_user.php. Performing a manipulation of the argument Username results in sql injection. This vulnerability is reported as CVE-2006-7088. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Simple PHP Forum up to 0.3 (Forum Software). It has been classified as critical. This affects an unknown code of the file logon_user.php. The manipulation of the argument username 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:
Multiple SQL injection vulnerabilities in Simple PHP Forum before 0.4 allow remote attackers to execute arbitrary SQL commands via the username parameter to (1) logon_user.php and (2) update_profile.php.
The weakness was disclosed 03/02/2007 (Website). The advisory is shared at sourceforge.net. This vulnerability is uniquely identified as CVE-2006-7088 since 02/27/2007. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. 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 highly functional. By approaching the search of inurl:logon_user.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 0.4 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at X-Force (30252). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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: Highly functional
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Simple PHP Forum 0.4
Suricata ID: 2004779
Suricata Class: 🔍
Suricata Message: 🔍
Timeline
02/27/2007 🔍03/02/2007 🔍
03/02/2007 🔍
03/13/2015 🔍
10/14/2017 🔍
Sources
Advisory: sourceforge.netStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2006-7088 (🔍)
GCVE (CVE): GCVE-0-2006-7088
GCVE (VulDB): GCVE-100-35277
X-Force: 30252 - Simple PHP Forum username SQL injection
Vupen: ADV-2006-4496
Entry
Created: 03/13/2015 12:16Updated: 10/14/2017 11:22
Changes: 03/13/2015 12:16 (51), 10/14/2017 11:22 (6)
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.