Skip to main content
Mallory
HighVulnerability

CVE-2009-2604: SQL Injection in Zen Help Desk 2.1 adminlogin.asp

Published Jul 27, 2009 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v2
EPSS0.93%61st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Zenhelpdesk
IdentifiersCVE-2009-2604CWE-89 · Improper Neutralization of Special…

Zen Help Desk 2.1 contains multiple SQL injection vulnerabilities in the adminlogin.asp script. Specifically, the 'userid' (also referred to as 'username') and 'PassWord' parameters passed to admin.asp are not properly sanitized, allowing remote attackers to inject and execute arbitrary SQL commands against the backend database.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to bypass authentication, extract sensitive information, modify or delete database contents, and potentially gain administrative access to the application.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to the admin interface via network controls, employ web application firewalls with SQL injection detection, and monitor logs for suspicious activity targeting the vulnerable parameters.

Remediation

Patch, then assume compromise.

Upgrade to a fixed version of Zen Help Desk, if available. Alternatively, modify the adminlogin.asp script to use parameterized queries or properly escape and validate all user-supplied input before including it in SQL statements.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ZenhelpdeskZen Help Deskapplication
FAQ

Frequently asked questions

Is CVE-2009-2604 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2009-2604 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2009-2604?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2009-2604. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2009-2604?
Upgrade to a fixed version of Zen Help Desk, if available. Alternatively, modify the adminlogin.asp script to use parameterized queries or properly escape and validate all user-supplied input before including it in SQL statements.
What products are affected by CVE-2009-2604?
Zenhelpdesk Zen Help Desk.
How severe is CVE-2009-2604?
CVE-2009-2604 has a CVSS v2 score of 7.5 (High) and an EPSS score of 0.93% (61st percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.