Ezy Helpdesk Ezyhelpdesk 1.0 Search Engine index.php search_string 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 Ezy Helpdesk Ezyhelpdesk 1.0. The affected element is an unknown function of the file index.php of the component Search Engine. Performing a manipulation of the argument search_string results in sql injection. This vulnerability is cataloged as CVE-2005-3826. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability classified as critical has been found in Ezy Helpdesk Ezyhelpdesk 1.0. This affects some unknown functionality of the file index.php of the component Search Engine. The manipulation of the argument search_string 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 Ezyhelpdesk 1.0 allow remote attackers to execute arbitrary SQL commands via the (1) edit_id, (2) faq_id, and (3) c_id parameters in a query string, and (4) the search engine, possibly involving the search_string parameter.

The weakness was shared 11/23/2005 by r0t (Website). It is possible to read the advisory at vupen.com. This vulnerability is uniquely identified as CVE-2005-3826 since 11/26/2005. 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 proof-of-concept. 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 Exploit-DB (26571), SecurityFocus (BID 15553†), OSVDB (21075†) and Secunia (SA17696†). The entry VDB-83200 is related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

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

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

11/23/2005 🔍
11/23/2005 +0 days 🔍
11/23/2005 +0 days 🔍
11/23/2005 +0 days 🔍
11/25/2005 +1 days 🔍
11/26/2005 +1 days 🔍
03/11/2015 +3392 days 🔍
07/03/2025 +3767 days 🔍

Sourcesinfo

Advisory: vupen.com⛔
Researcher: r0t
Status: Not defined

CVE: CVE-2005-3826 (🔍)
GCVE (CVE): GCVE-0-2005-3826
GCVE (VulDB): GCVE-100-27099
SecurityFocus: 15553 - Ezyhelpdesk Multiple SQL Injection Vulnerabilities
Secunia: 17696 - Ezyhelpdesk Multiple SQL Injection Vulnerabilities, Less Critical
OSVDB: 21075 - Ezyhelpdesk index.php Multiple Parameter SQL Injection
Vupen: ADV-2005-2560

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

Entryinfo

Created: 03/11/2015 23:39
Updated: 07/03/2025 19:35
Changes: 03/11/2015 23:39 (54), 07/13/2018 08:27 (8), 07/03/2025 19:35 (24)
Complete: 🔍
Cache ID: 216:6FA:103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!