dbcve.org
ZnunyApplication

CVE-2024-48937

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-11
Fix available
A fix is available. Upgrade to 6.1.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Znuny before LTS 6.5.1 through 6.5.10 and 7.0.1 through 7.0.16 allows XSS. JavaScript code in the short description of the SLA field in Activity Dialogues is executed.

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

Znuny LTS before 6.5.11 and 7.0.17 contains a stored XSS vulnerability in the short description field of SLA settings within Activity Dialogues. User-supplied JavaScript code in this field is not properly sanitized and executes when the Activity Dialog is rendered.

MitigationUpgrade to Znuny LTS 6.5.11, 7.0.17, or later; alternatively, implement output encoding/sanitization on the SLA short description field before rendering.

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
ZnunyApplication
Affected:>= 6.0.0, < 6.1.0>= 6.5.1, <= 6.5.10>= 7.0.1, <= 7.0.16

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 the installed Znuny LTS version
    Access the Znuny admin interface, typically via Admin > System Administration > System Information, or check the /opt/znuny/Kernel/Config.pm file for the ProductVersion setting
    Affected if The installed version is 6.0.0 to < 6.1.0, 6.5.1 to 6.5.10, or 7.0.1 to 7.0.16
  2. Determine if Activity Dialogues with SLA are configured
    Navigate to Admin > Process Management > Activity Dialogues and check if any Activity Dialogues contain SLA configuration elements
    Affected if Activity Dialogues exist that reference or include SLA settings
  3. Inspect SLA short description fields for unsanitized content
    Access the SLA management interface (Admin > SLA Management) or query the sla_table in the database for the ShortDescription field, reviewing any entries for script tags, javascript: URIs, or event handler attributes
    Affected if Any SLA short description contains raw HTML, script tags, or JavaScript event handlers that would execute when rendered in an Activity Dialog
  4. Check database storage of SLA configuration
    Query the database table storing SLA configuration data, looking at columns related to short description or user-facing SLA fields for any injected XSS payloads
    Affected if Database records contain encoded or raw XSS payloads in SLA-related description fields

A user is affected if their Znuny LTS version falls within the vulnerable ranges AND Activity Dialogues with SLA settings exist AND the SLA short description field contains unsanitized script content that would execute when the Activity Dialog is displayed.

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.

dbcve · scoped
Upgrade available Upgrade to 6.1.0 or later
Fixed in 6.1.0
Interim mitigation

Upgrade to Znuny LTS 6.5.11, 7.0.17, or later; alternatively, implement output encoding/sanitization on the SLA short description field before rendering.

Recommended fix Moderate confidence

Znuny 6.5.11+ or 7.0.17+ (latest stable respective branch)

  1. 1. Identify the current Znuny version by checking the system information in the admin interface or using the command line package manager.
  2. 2. For Znuny 6.x installations: Upgrade to version 6.5.11 or later (or the latest 6.5.x stable release).
  3. 3. For Znuny 7.x installations: Upgrade to version 7.0.17 or later (or the latest 7.0.x stable release).
  4. 4. For Znuny 6.0.x to 6.1.x: Upgrade to the latest 6.5.x stable release to address both the 6.0.x/6.1.x and 6.5.x vulnerabilities.
  5. 5. After upgrade, verify the SLA field in Activity Dialogues properly escapes HTML/JavaScript in the short description field.
  6. 6. Test the Activity Dialogues functionality to ensure the XSS fix does not break legitimate SLA management workflows.
Caveat Review release notes for any functionality changes between current version and target upgrade version before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Znuny Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-48937 — 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-48937 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