Skip to main content
CVE-2024-32492VulnerabilityPublished Updated

CVE-2024-32492: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

1. Immediately review and restrict permissions for users accessing the customer front-end to minimize exposure. 2. Implement strict Content Security Policy (CSP) headers to block execution of unauthorized external scripts. 3. Conduct input validation and sanitization on all user-supplied data displayed in the ticket detail view to prevent injection of malicious JavaScript. 4. Monitor web application logs and network traffic for unusual or suspicious activity indicative of exploitation attempts. 5. Isolate the ticketing system network segment to limit external access where feasible. 6. Engage with Znuny community or vendor channels for patches or official updates and apply them promptly once available. 7. Consider deploying Web Application Firewalls (WAF) with custom rules to detect and block exploitation patterns. 8. Educate support staff and users about phishing and social engineering risks that could leverage this vulnerability. 9. Prepare incident response plans specific to web application compromise scenarios involving script injection.

Description

An issue was discovered in Znuny 7.0.1 through 7.0.16 where the ticket detail view in the customer front allows the execution of external JavaScript.

References

Community reviews

Loading reviews…