Skip to main content
VulnerabilityPublished

CVE-2026-18363: Logic Vulnerability

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-18363· Critical 9.1

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

Data as of 29 Oct 2026, 07:15 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 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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. Weaponized: 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 29 Oct 2026.

What to do

Upgrade 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

AI-suggested

A fix is available in osTicket versions v1.17.8 and v1.18.4 that corrects the token expiry validation logic. Users should upgrade to these or later versions to remediate the vulnerability. Patch status is not explicitly confirmed beyond these versions; verify with the vendor advisory for the latest remediation guidance.

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…