CVE-2025-53959
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 · uneditedIn JetBrains YouTrack before 2025.2.86069, 2024.3.85077, 2025.1.86199 email spoofing via an administrative API was possible
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 · moderate confidenceIn JetBrains YouTrack before versions 2025.2.86069, 2024.3.85077, and 2025.1.86199, an administrative API allowed email spoofing, enabling attackers to send emails that appear to originate from legitimate YouTrack addresses.
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< 2024.3.85077>= 2025.1.62455, < 2025.1.86199CVSS 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
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/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 YouTrack versionAccess the YouTrack administration interface and navigate to 'About' section, or check the version from the startup logs at <youtrack_install>/logs/youtrack*.logAffected if The installed version is before 2024.3.85077, OR is between 2025.1.62455 and 2025.1.86199 (exclusive)
-
Verify administrative API accessibilityCheck if the YouTrack administrative API endpoint at /api/admin is exposed to untrusted networks or accessible without proper authentication. Review network firewall rules and YouTrack security configuration.Affected if The administrative API is accessible from untrusted networks or external IP addresses without strict access controls
-
Confirm external email configurationReview YouTrack email settings under 'Administration > Mail' to determine if outgoing email is configured and which SMTP servers are usedAffected if Outgoing email is enabled and configured, as this is required for the spoofed emails to be sent through YouTrack infrastructure
-
Audit administrative user accountsCheck the administrative user list in 'Administration > Users' for any unauthorized or unexpected accounts, particularly those with email privilegesAffected if Unexpected administrative accounts exist with permission to send emails
You are affected if your YouTrack version falls within the vulnerable ranges AND the administrative API is accessible to potential attackers AND outgoing email is configured.
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 · scoped2024.3.850772025.1.86199
Upgrade YouTrack to version 2025.2.86069, 2024.3.85077, 2025.1.86199 or later to patch the administrative API email spoofing vulnerability.
2024.3.85077, 2025.1.86199, or 2025.2.86069 (depending on which version branch you are currently on)
- 1. Identify the current YouTrack version by accessing Administration > Diagnostics > System Info
- 2. Based on the current version, determine the appropriate upgrade path: if running < 2024.3, upgrade to 2024.3.85077 or later; if running 2025.1.x, upgrade to 2025.1.86199 or later; if running 2025.2.x or earlier, upgrade to 2025.2.86069 or later
- 3. Back up the YouTrack database and configuration files before upgrading
- 4. Download the fixed YouTrack version from the official JetBrains website (https://www.jetbrains.com/youtrack/download/)
- 5. Stop the YouTrack service
- 6. Install the new version following the standard upgrade procedure (run the installer and follow prompts, or use the upgrade command)
- 7. Start the YouTrack service
- 8. Verify the upgrade was successful by checking the version in Administration > Diagnostics > System Info
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53959 — 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-53959 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