dbcve.org
YoutrackApplication · Jetbrains

CVE-2025-54527

MEDIUM · 6.1 CVSS v3.1 Published 2025-07-28
Fix available
A fix is available. Upgrade to 2025.2.86935 / 2025.2.87167 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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.2.86935, 2025.2.87167, 2025.3.87341, 2025.3.87344 improper iframe configuration in widget sandbox allows popups to bypass security restrictions

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.2.86935, 2025.2.87167, 2025.3.87341, and 2025.3.87344 contain an improper iframe sandbox configuration in the widget system. This allows embedded widget content to open popup windows that bypass normal browser security restrictions, potentially enabling phishing attacks or unauthorized window spawning.

MitigationUpgrade YouTrack to version 2025.2.86935, 2025.2.87167, 2025.3.87341, 2025.3.87344 or later, which includes proper iframe sandbox attributes to prevent popup bypass.

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.2.86935>= 2025.2.87000, < 2025.2.87167>= 2025.3, < 2025.3.87341

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify installed YouTrack version
    Access YouTrack admin interface via [your-youtrack-url]/admin/system or check the product version from the installation directory/conf file
    Affected if The installed version falls into any of these ranges: < 2025.2.86935; >= 2025.2.87000 and < 2025.2.87167; >= 2025.3 and < 2025.3.87341
  2. Verify widget system is in use
    Check if custom widgets or third-party widgets are enabled in YouTrack administration under 'Widgets' or 'Customization' settings
    Affected if The widget system is active and contains widgets with embedded content
  3. Inspect iframe sandbox configuration
    Examine widget configuration files or admin UI for iframe/sandbox attributes. Look for missing 'sandbox' attribute or sandbox values that allow 'allow-popups'
    Affected if Widget iframe elements lack proper sandbox restrictions or explicitly enable popup capabilities

You are affected if your YouTrack version is in a vulnerable range AND the widget system is enabled with improperly sandboxed iframe configurations.

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.2.86935 / 2025.2.87167 / 2025.3.87341 or later
Fixed in 2025.2.869352025.2.871672025.3.87341
Interim mitigation

Upgrade YouTrack to version 2025.2.86935, 2025.2.87167, 2025.3.87341, 2025.3.87344 or later, which includes proper iframe sandbox attributes to prevent popup bypass.

Recommended fix High confidence

2025.3.87344 (or the appropriate fixed version for your branch: 2025.2.86935 or 2025.2.87167)

  1. 1. Identify the current YouTrack version by navigating to Administration > Troubleshooting > System Info
  2. 2. Create a complete backup of the YouTrack database and configuration files before upgrading
  3. 3. Download the appropriate fixed version from jetbrains.com/youtrack/download (choose 2025.2.86935, 2025.2.87167, or the latest 2025.3.87344 based on your upgrade path)
  4. 4. Stop the YouTrack service
  5. 5. Install the downloaded fixed version following the standard YouTrack upgrade procedure
  6. 6. Start the YouTrack service
  7. 7. Verify the upgrade was successful by checking the version in Administration > Troubleshooting > System Info
  8. 8. Confirm the iframe widget sandbox configuration no longer allows popup bypass by testing widget functionality

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

Fix this in Youtrack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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