dbcve.org
YoutrackApplication · Jetbrains

CVE-2025-48391

HIGH · 7.5 CVSS v3.1 Published 2025-05-20
Fix available
A fix is available. Upgrade to 2025.1.76253 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
In JetBrains YouTrack before 2025.1.76253 deletion of issues was possible due to missing permission checks in API

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

JetBrains YouTrack versions prior to 2025.1.76253 contain a missing authorization check in certain API endpoints that allows unauthenticated or unauthorized users to delete issues via the REST API without proper permission validation.

MitigationUpgrade YouTrack to version 2025.1.76253 or later to obtain the vendor patch that implements proper permission checks on issue deletion API operations.

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
YoutrackApplication
Affected:< 2025.1.76253

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Identify YouTrack installation version
    Access the YouTrack administration area or check the version information page (typically at /about or through the admin dashboard). The version number is displayed in the format YYYY.X.XXXXX.
    Affected if The installed version is lower than 2025.1.76253 (for example, 2025.1.75000 or any earlier release).
  2. Confirm REST API is accessible
    Attempt to reach the YouTrack REST API endpoint (typically at /api/issues or /api/admin). An HTTP 200 or 401 response indicates the API is available.
    Affected if The REST API responds to requests, indicating it is enabled and exposed.
  3. Verify issue deletion endpoint exposure
    Send a test request to the issue deletion API endpoint (DELETE method to /api/issues/{issue-id}) without providing authentication credentials.
    Affected if The request completes without returning an authentication or authorization error, suggesting the endpoint accepts requests without proper permission validation.

Your YouTrack instance is affected if it runs any version prior to 2025.1.76253 and the REST API is accessible, as the missing authorization check could allow unauthorized issue deletion.

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 2025.1.76253 or later
Fixed in 2025.1.76253
Interim mitigation

Upgrade YouTrack to version 2025.1.76253 or later to obtain the vendor patch that implements proper permission checks on issue deletion API operations.

Recommended fix High confidence

YouTrack 2025.1.76253 or later

  1. 1. Check the current YouTrack version by accessing the Administration > System section or viewing the version info in the YouTrack InCloud dashboard
  2. 2. Ensure you have a complete backup of your YouTrack data before upgrading
  3. 3. Download YouTrack version 2025.1.76253 or a later stable release from the official JetBrains website (www.jetbrains.com/youtrack/download)
  4. 4. For YouTrack InCloud: The fix is deployed automatically when JetBrains rolls out the fixed version to your instance - contact support if immediate action is needed
  5. 5. For YouTrack InHouse/Standalone: Follow the standard upgrade procedure in the JetBrains documentation to install the updated version
  6. 6. After upgrade, verify that the API endpoint for issue deletion now properly enforces permission checks
  7. 7. Confirm that users without proper deletion permissions can no longer delete issues via the API
Caveat Review the JetBrains YouTrack 2025.1 release notes for any other changes that may affect your configuration or integrations

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

Fix this in Youtrack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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