dbcve.org
OsticketApplication · Enhancesoft

CVE-2020-24881

CRITICAL · 9.8 CVSS v3.1 Published 2020-11-02
Fix available
A fix is available. Upgrade to 1.14.3 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

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
SSRF exists in osTicket before 1.14.3, where an attacker can add malicious file to server or perform port scanning.

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

A Server-Side Request Forgery (SSRF) vulnerability exists in osTicket versions prior to 1.14.3. The flaw allows remote attackers to make the server perform arbitrary requests, potentially enabling upload of malicious files to the server or internal network reconnaissance via port scanning.

MitigationUpgrade osTicket to version 1.14.3 or later to remediate this SSRF vulnerability. If immediate patching is not possible, restrict outbound network access from the application server and implement input validation on file upload endpoints.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OsticketApplication
Affected:< 1.14.3

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify installed osTicket version
    Log into the osTicket admin panel and navigate to the Dashboard or Help > About section to view the software version. Alternatively, check the include/VERSION.php file in the web root if accessible.
    Affected if The displayed version number is lower than 1.14.3 (for example, 1.14.2, 1.14.1, 1.13.x, etc.)
  2. Verify file attachment upload functionality
    Navigate to the osTicket admin panel and go to Settings > Attachments or File Settings. Check if the attachment feature is enabled and review allowed attachment sources.
    Affected if Attachments are enabled and the system accepts URLs or remote file sources as part of the upload mechanism
  3. Check for exposed network request features
    Inspect the osTicket configuration file (ost-config.php or config.php in the include directory) for settings related to URL fetching, proxy configuration, or remote attachment handling.
    Affected if The configuration contains settings that allow the server to fetch remote resources or URLs during file upload operations
  4. Review web server access for SSRF endpoints
    Examine the osTicket source code in the include/class.file.php or upload handling scripts for functions that process URL parameters or allow remote file retrieval. Look for file_get_contents, curl, or similar functions handling user-supplied URLs.
    Affected if The code contains handlers that accept URL parameters for file uploads without proper validation

A user is affected if their osTicket installation shows a version lower than 1.14.3 AND the attachment/upload feature that accepts remote URLs is enabled.

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
Upgrade available Upgrade to 1.14.3 or later
Fixed in 1.14.3
Vendor patch github.com →
Interim mitigation

Upgrade osTicket to version 1.14.3 or later to remediate this SSRF vulnerability. If immediate patching is not possible, restrict outbound network access from the application server and implement input validation on file upload endpoints.

Recommended fix High confidence

osTicket 1.14.3 or later

  1. 1. Create a complete backup of the osTicket database and files
  2. 2. Download osTicket version 1.14.3 or later from the official repository (https://github.com/osTicket/osTicket/releases)
  3. 3. Review the official upgrade guide at https://docs.osticket/en/latest/Admin/Guide/Upgrade.html
  4. 4. Replace the existing osTicket files with the new version files, preserving the configuration and upload directories
  5. 5. Run any database migration scripts if required by the upgrade
  6. 6. Verify the upgrade was successful by logging in and testing core functionality
  7. 7. Confirm the SSRF vulnerability is patched by verifying the fix from commit d98c2d096aeb8876c6ab2f88317cd371d781f14d is applied
Caveat Review release notes for your specific upgrade path; major version jumps may include breaking changes to plugins or integrations

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

Fix this in Osticket Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-24881 — 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-2020-24881 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