eFiction 1.0/1.1/2.0 titles.php let sql injection

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.6$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in eFiction 1.0/1.1/2.0. This impacts an unknown function of the file titles.php. This manipulation of the argument let causes sql injection. This vulnerability is handled as CVE-2005-4168. The attack can be initiated remotely. Additionally, an exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in eFiction 1.0/1.1/2.0. It has been declared as critical. Affected by this vulnerability is some unknown functionality of the file titles.php. The manipulation of the argument let 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:

Multiple SQL injection vulnerabilities in eFiction 1.0, 1.1, and 2.0 allow remote attackers to execute arbitrary SQL commands via (1) the let parameter in a viewlist action to titles.php and (2) the username.

The bug was discovered 11/25/2005. The weakness was released 11/25/2005 by rgod (Website). The advisory is shared at rgod.altervista.org. This vulnerability is known as CVE-2005-4168 since 12/11/2005. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

After even before and not, there has been an exploit disclosed. It is possible to download the exploit at securityfocus.com. It is declared as proof-of-concept. By approaching the search of inurl:titles.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 20349 (eFiction < 2.0.2 Multiple Remote Vulnerabilities (SQLi, XSS, Disc)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CGI abuses and running in the context r.

Upgrading eliminates this vulnerability. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 3593.

The vulnerability is also documented in the databases at X-Force (23373), Exploit-DB (26592), Tenable (20349), SecurityFocus (BID 15568†) and OSVDB (21120†). Entries connected to this vulnerability are available at VDB-27427, VDB-27426, VDB-27425 and VDB-27424. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.6

VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Sql injection
CWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 20349
Nessus Name: eFiction < 2.0.2 Multiple Remote Vulnerabilities (SQLi, XSS, Disc)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍
TippingPoint: 🔍

Timelineinfo

11/25/2005 🔍
11/25/2005 +0 days 🔍
11/25/2005 +0 days 🔍
11/25/2005 +0 days 🔍
11/25/2005 +0 days 🔍
11/25/2005 +0 days 🔍
11/28/2005 +2 days 🔍
11/28/2005 +0 days 🔍
12/11/2005 +12 days 🔍
12/11/2005 +0 days 🔍
12/29/2005 +18 days 🔍
01/04/2006 +6 days 🔍
03/11/2015 +3353 days 🔍
06/22/2025 +3756 days 🔍

Sourcesinfo

Advisory: rgod.altervista.org
Researcher: rgod
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2005-4168 (🔍)
GCVE (CVE): GCVE-0-2005-4168
GCVE (VulDB): GCVE-100-27421
X-Force: 23373
SecurityFocus: 15568 - eFiction Multiple Input Validation Vulnerabilities
Secunia: 17777 - eFiction Multiple Vulnerabilities, Highly Critical
OSVDB: 21120 - eFiction titles.php let Parameter SQL Injection
SecurityTracker: 1015273
Vulnerability Center: 10109 - eFiction SQL Injections via \, Medium

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 03/11/2015 23:39
Updated: 06/22/2025 17:19
Changes: 03/11/2015 23:39 (81), 06/13/2019 09:12 (3), 06/22/2025 17:19 (19)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!