dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-36214

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-14
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
osTicket versions from 1.10 up to 1.17.7 and from 1.18.0 up to 1.18.3 are vulnerable to a stored XSS due to a vulnerable Bootstrap Tooltip component and insufficient HTML sanitization, allowing remote attackers to execute arbitrary JavaScript in Agent or Admin sessions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

osTicket versions 1.10-1.17.7 and 1.18.0-1.18.3 contain a stored XSS vulnerability stemming from an insecure Bootstrap Tooltip component combined with inadequate HTML sanitization. Attackers can inject malicious JavaScript that executes when Agent or Admin users view compromised content.

MitigationUpgrade osTicket to version 1.18.4 or later. Additionally, audit existing ticket content for malicious payloads that may have been injected prior to patching.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate osTicket version file
    Check the version file at include/version.php or scp/ost-config.php for a line defining the version constant, or log into the admin panel and navigate to the System Information page
    Affected if The version displayed is 1.10 through 1.17.7, or 1.18.0 through 1.18.3
  2. Confirm version number manually
    Open include/version.php and look for a definition like define('VERSION','x.x.x') or similar version declaration
    Affected if The version number falls within 1.10-1.17.7 or 1.18.0-1.18.3
  3. Verify Agent or Admin access exists
    Check if any user accounts with Agent or Admin roles exist in the system by querying the ost_staff table in the database or reviewing user roles in the admin panel
    Affected if The system has active Agent or Admin accounts who can view ticket content, as this is required to trigger the XSS payload
  4. Check Bootstrap Tooltip implementation
    Search the codebase for Bootstrap Tooltip initialization calls, particularly in ticket view templates or JavaScript files handling user-submitted content display
    Affected if Tooltip functionality is present and handles content that could contain unsanitized user input from tickets

You are affected if your installed osTicket version is 1.10-1.17.7 or 1.18.0-1.18.3 and Agents or Admins can view tickets containing user-submitted content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade osTicket to version 1.18.4 or later. Additionally, audit existing ticket content for malicious payloads that may have been injected prior to patching.

Recommended fix High confidence

osTicket 1.18.4 or later (latest stable release)

  1. 1. Backup your current osTicket installation and database before proceeding with any upgrade.
  2. 2. Download the latest stable version of osTicket from the official GitHub repository (github.com/osTicket/osTicket) or osticket.com.
  3. 3. Review the official release notes for version 1.18.4 or later to understand any migration requirements.
  4. 4. Upgrade your osTicket installation to version 1.18.4 or the latest stable release.
  5. 5. After upgrading, verify that the Bootstrap Tooltip component has been updated and HTML sanitization is properly implemented.
  6. 6. Test the fix by attempting to inject malicious JavaScript in input fields that were previously vulnerable (e.g., ticket subjects, user fields).
  7. 7. Clear all browser caches and sessions to ensure the fix takes full effect.
Caveat Review release notes for any configuration or plugin changes between 1.18.3 and the target version; some plugins may require updates

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-36214 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-36214 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data