Skip to main content
VulnerabilityPublished

CVE-2025-45387: osTicket · Cross-site Scripting

Source CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium : upgrade to 1.17.6 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.17.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jun 2025

  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 26 Oct 2026.

What to do

Upgrade osticket/osTicket to 1.17.6.

Affected software

ProductAffectedFixed in
GitHubosticket/osTicketpkg:github/osticket/osTicketOther threatsAffected
  • <1.17.6
  • =1.18.2
Fixed in
  • 1.17.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should prioritize upgrading osTicket installations to versions 1.17.6 or 1.18.2 or later, where this vulnerability is patched. In the absence of immediate patching, organizations should implement strict access controls and monitor user activities on the /scp/ajax.php endpoint to detect anomalous behavior. Limiting the number of users with low-level privileges and enforcing strong authentication mechanisms can reduce the risk of exploitation. Additionally, applying web application firewalls (WAFs) with rules targeting suspicious AJAX requests may help mitigate exploitation attempts. Regular security audits and code reviews of customizations to osTicket should be conducted to ensure no additional access control weaknesses exist. Logging and alerting on unusual access patterns to the support portal can facilitate early detection of exploitation attempts. Finally, educating users about the risks of social engineering and ensuring minimal user interaction is required for sensitive operations can further reduce exposure.

Description

osTicket prior to v1.17.6 and v1.18.2 are vulnerable to Broken Access Control Vulnerability in /scp/ajax.php.

References

Community reviews

Loading reviews…