Enterprise ServerApplication · GitHub
CVE-2025-13744
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 · uneditedAn Improper Neutralization of Input During Web Page Generation vulnerability was identified in GitHub Enterprise Server that allowed attacker controlled HTML to be rendered by the Filter component (search) across GitHub that could be used to exfiltrate sensitive information. An attacker would require permissions to create or modify the names of milestones, issues, pull requests, or similar entities that are rendered in the vulnerable filter/search components. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.20 and was fixed in versions 3.19.1, and 3.18.2, 3.17.8, 3.16.11, 3.15.15, and 3.14.20. This vulnerability was reported via the GitHub Bug Bounty program.
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in GitHub Enterprise Server's Filter/Search component. Attackers with permissions to create or modify entity names (milestones, issues, pull requests) can inject malicious HTML that gets rendered without proper sanitization when these entities appear in search results, enabling sensitive data exfiltration.
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
Enterprise ServerApplication
>= 3.14.0, < 3.14.20>= 3.15.0, < 3.15.15>= 3.16.0, < 3.16.11>= 3.17.0, < 3.17.8>= 3.18.0, < 3.18.2= 3.19.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify GitHub Enterprise Server versionAccess the GitHub Enterprise Server admin console, go to the dashboard or site administration page, and locate the version number. Alternatively, run 'ghe-version' from the server command line if you have SSH access.Affected if The installed version is >= 3.14.0 and < 3.14.20, OR >= 3.15.0 and < 3.15.15, OR >= 3.16.0 and < 3.16.11, OR >= 3.17.0 and < 3.17.8, OR >= 3.18.0 and < 3.18.2, OR equals 3.19.0
-
Verify search filter component is accessibleConfirm that the search/filter functionality is available on the instance by accessing the search bar in the GitHub web interface or using the search API endpoint.Affected if The search feature is active and accessible to users with permissions to create or modify milestones, issues, or pull requests
-
Audit existing milestones for unsanitized contentNavigate to the repository or organization settings and review all milestone names and descriptions. Check for any HTML tags, script elements, or suspicious JavaScript event handlers in milestone fields.Affected if Any milestone contains raw HTML, <script> tags, or event handler attributes like onload, onerror, or onclick that could execute JavaScript
-
Audit existing issues and pull requests for unsanitized contentReview recent issues and pull request titles, descriptions, and comments through the web interface or API. Look for injected HTML or script tags that would render when appearing in search results.Affected if Any issue or pull request contains unsanitized HTML or script elements that would execute when rendered in search results
The environment is affected if the installed GitHub Enterprise Server version falls within any of the vulnerable ranges AND the search/filter feature is in use with user-created milestones, issues, or pull requests that may contain injected malicious content.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.14.203.15.153.16.11
Upgrade GitHub Enterprise Server to one of the fixed versions (3.19.1, 3.18.2, 3.17.8, 3.16.11, 3.15.15, or 3.14.20) or later. Review user permissions for milestone, issue, and pull request creation/modification to limit exposure.
Upgrade to GitHub Enterprise Server version 3.14.20, 3.15.15, 3.16.11, 3.17.8, 3.18.2, or 3.19.1 (or later) depending on your current major version branch
- 1. Back up your GitHub Enterprise Server instance data and configuration before proceeding with any upgrade.
- 2. Identify your current GitHub Enterprise Server version by navigating to the admin console or checking system settings.
- 3. Review the GitHub Enterprise Server upgrade documentation at docs.github.com for your specific version path.
- 4. For version 3.14.x: upgrade to version 3.14.20 or later.
- 5. For version 3.15.x: upgrade to version 3.15.15 or later.
- 6. For version 3.16.x: upgrade to version 3.16.11 or later.
- 7. For version 3.17.x: upgrade to version 3.17.8 or later.
- 8. For version 3.18.x: upgrade to version 3.18.2 or later.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Enterprise Server
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13744 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13744 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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