CVE-2005-0487
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-site scripting (XSS) vulnerability in index.php for Kayako ESupport 2.3.1, and possibly other versions, allows remote attackers to inject arbitrary HTML and web script via the nav parameter.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-site scripting (XSS) vulnerability in Kayako ESupport 2.3.1's index.php allows remote attackers to inject arbitrary HTML and web script via the nav parameter. This occurs because user-supplied input in the nav parameter is not properly sanitized before being reflected in the HTML output.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Kayako ESupport installationLook for the Kayako ESupport web application in your web server's document root or hosting directory. Common paths include /esupport, /support, or the root web directory.Affected if Kayako ESupport is not installed on the server
-
Verify the exact version numberCheck the product version by viewing source files, admin panel, or version information file. In version 2.3.1, look for a version.php or similar file that displays '2.3.1' or check the index.php header/footer for the version string.Affected if The installed version is not exactly 2.3.1 (only this specific version is affected)
-
Locate index.phpFind the index.php file in the ESupport installation directory. This is typically in the main ESupport folder.Affected if index.php does not exist in the ESupport installation path
-
Check if nav parameter is processedExamine the index.php source code for handling of the 'nav' GET or POST parameter. Look for code that takes the nav parameter value and outputs it directly to HTML without sanitization functions such as htmlspecialchars() or similar encoding.Affected if The nav parameter is reflected in HTML output without proper sanitization (the vulnerable condition)
-
Test for XSS via nav parameterSend a request to index.php with a crafted nav parameter such as nav=<script>alert('xss')</script> and inspect the response to see if the script tag is rendered unescaped in the HTML output.Affected if The response contains the unsanitized nav parameter value and executes the injected script
You are affected only if Kayako ESupport version 2.3.1 is installed AND the index.php file processes the nav parameter without sanitizing it before HTML output.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper input validation and output encoding for the nav parameter in index.php. All user-supplied input should be sanitized using HTML entity encoding or a web application firewall should be considered as a temporary measure.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-0487 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2005-0487 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data