dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-46639

HIGH · 7.6 CVSS v3.1 Published 2024-09-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
A cross-site scripting (XSS) vulnerability in HelpDeskZ v2.0.2 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Name text field of Custom Fields message box.

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 confidence

A stored cross-site scripting (XSS) vulnerability in HelpDeskZ v2.0.2 allows authenticated attackers to inject arbitrary JavaScript or HTML into the Name text field of Custom Fields. This malicious payload is stored in the database and executed when other users view pages displaying the affected custom fields.

MitigationImplement strict input validation and context-aware output encoding for the Custom Fields Name parameter to neutralize malicious payloads before storage and before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify HelpDeskZ installation
    Check for HelpDeskZ files (typically in web root, look for helpdeskz folder or files like index.php, config.php with 'helpdeskz' references)
    Affected if HelpDeskZ software is present on the server
  2. Confirm HelpDeskZ version
    Locate version file or check version disclosed in login page footer, admin dashboard, or changelog file. Compare against v2.0.2
    Affected if Installed version is v2.0.2 or falls within the affected range around this version
  3. Verify custom fields functionality exists
    Log into HelpDeskZ admin panel and navigate to Custom Fields settings (usually under Settings > Custom Fields or similar). Check if the Custom Fields module is present and accessible
    Affected if Custom Fields feature exists and is accessible in the admin interface
  4. Inspect Custom Fields Name entries for malicious payloads
    Query the database table storing custom fields (typically 'cfg_custom_fields' or similar). Examine the 'name' field for suspicious patterns like <script>, javascript:, onload, onerror, or encoded characters
    Affected if Any Custom Field Name contains executable JavaScript or HTML tags that were not intentionally authored
  5. Check for stored XSS execution context
    As an authenticated user (non-admin), navigate to ticket submission or view pages that display custom fields. Inspect page source for unencoded output of custom field names
    Affected if Custom Field Name values are rendered without proper HTML encoding

User is affected if HelpDeskZ v2.0.2 is installed and Custom Fields contain injected XSS payloads in the Name field that render without encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and context-aware output encoding for the Custom Fields Name parameter to neutralize malicious payloads before storage and before rendering.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-46639 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-46639 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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