Skip to main content
VulnerabilityPublished

CVE-2026-18363: Enhancesoft osTicket · Weak Password Recovery

Affects Enhancesoft osTicketSource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical : upgrade to 1.18.4 or 1.17.8 as a priority.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-07-30.

Patch
Available – fixed in 1.18.4, 1.17.8
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jul 2026

  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 Enhancesoft osTicket to 1.18.4 or 1.17.8.

Affected software

ProductAffectedFixed in
Enhancesoft LLCosTicketAffected
  • <1.18.4
Fixed in
  • 1.18.4
Enhancesoft LLCosTicketAffected
  • <1.17.8
Fixed in
  • 1.17.8

Description

A logic vulnerability in the password reset token validation routine implemented by osTicket in versions prior to v1.17.8 and v1.18.4. During the password reset process, the application retrieves the timestamp associated with the provided token and checks whether the configured validity period has expired. Consequently, the expiry check is only performed if the timestamp lookup fails, allowing tokens with an existing timestamp to bypass the intended expiry validation. Therefore, an attacker able to obtain a valid password reset token could reuse it to perform an unauthorised password reset and compromise the affected account.

References

Community reviews

Loading reviews…