| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Gurur haber 2.0 and classified as critical. This affects an unknown function of the file uyeler2.php. Performing a manipulation of the argument ID results in sql injection. This vulnerability is known as CVE-2007-4491. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
Details
A vulnerability classified as critical has been found in Gurur haber 2.0. This affects an unknown part of the file uyeler2.php. The manipulation of the argument id 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 uyeler2.php in Gurur haber 2.0 allows remote attackers to execute arbitrary SQL commands via the id parameter.
The weakness was published 08/20/2007 (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2007-4491 since 08/22/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 and a public exploit are known. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
The exploit is shared for download at exploit-db.com. It is declared as highly functional. By approaching the search of inurl:uyeler2.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 X-Force (36114), Exploit-DB (30511), SecurityFocus (BID 25368†) and OSVDB (38333†). 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: 7.3VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
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: 🔍
Access: Public
Status: Highly functional
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/20/2007 🔍08/20/2007 🔍
08/22/2007 🔍
08/22/2007 🔍
11/01/2007 🔍
03/16/2015 🔍
09/06/2025 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2007-4491 (🔍)
GCVE (CVE): GCVE-0-2007-4491
GCVE (VulDB): GCVE-100-38475
X-Force: 36114 - Gurur Haber uyeler2.php SQL injection
SecurityFocus: 25368
OSVDB: 38333 - Gurur haber uyeler2.php id Parameter SQL Injection
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/16/2015 12:18Updated: 09/06/2025 04:26
Changes: 03/16/2015 12:18 (51), 11/02/2017 10:49 (4), 09/06/2025 04:26 (20)
Complete: 🔍
Cache ID: 216:232: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.