CVE-2024-48937

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.

Published: 2024-10-11 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-48937 is rated Low Risk (33.1/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.36%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-48937

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 1.52% 0.36% -1.16%
2 2026-03-02 1.13% 1.52% +0.40%
3 2026-03-01 — 1.13% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-48937

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.1 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 2.7 [email protected]
6.1 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 2.7 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-48937

OS Trackers for CVE-2024-48937

vendor priority summary link
debian not yet assigned CVE-2024-48937 not yet assigned priority: Debian including 1 source packages (znuny), 4 status rows across 4 suites (bookworm, forky, sid, trixie): resolved 3, open 1. https://security-tracker.debian.org/tracker/CVE-2024-48937
ubuntu medium CVE-2024-48937 medium priority: Ubuntu including 1 source packages (znuny), 7 status rows across 7 suites (focal, jammy, noble, oracular, plucky, questing, upstream): DNE 2, not-affected 2, ignored 1, needs-triage 1, released 1. https://ubuntu.com/security/CVE-2024-48937

Affected software / configurations for CVE-2024-48937

Vendor Product Version Raw CPE
znuny znuny >= 6.0.0, < 6.1.0 cpe:2.3:a:znuny:znuny:*:*:*:*:lts:*:*:*
znuny znuny >= 6.5.1, <= 6.5.10 cpe:2.3:a:znuny:znuny:*:*:*:*:lts:*:*:*
znuny znuny >= 7.0.1, <= 7.0.16 cpe:2.3:a:znuny:znuny:*:*:*:*:-:*:*:*

References for CVE-2024-48937

cvelogic Threat Intelligence