CVE-2025-64684
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.3.104432 information disclosure was possible via the feedback form
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 versions prior to 2025.3.104432, the feedback form contained a vulnerability allowing unauthorized access to sensitive information. The specific nature of the disclosure (e.g., other users' submissions, system data, or internal metadata) is not detailed in available sources, but the flaw allows an attacker with access to the feedback mechanism to obtain information they should not have.
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< 2025.3.104432CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installation locationLocate the YouTrack installation directory. Common paths include /opt/youtrack, /home/youtrack, or C:\YouTrack on Windows. Check for the youtrack.jar or youtrack.sh startup script.Affected if YouTrack is installed and running
-
Determine installed YouTrack versionAccess the YouTrack administration dashboard, or check the version from the startup logs. The version is typically displayed on the login page footer or in Admin > About. You can also check the youtrack.jar file properties or the version file in the installation directory.Affected if The version displayed is below 2025.3.104432
-
Verify version is in affected rangeCompare your identified version number against the vulnerable range: any version prior to 2025.3.104432. Note that version numbers follow the format YYYY.R.build (e.g., 2025.2.98765).Affected if Your installed version is less than 2025.3.104432
-
Confirm feedback form accessibilityLog in to YouTrack as a standard user or unauthenticated access if allowed. Navigate to the feedback form, typically found at /feedback or accessible from the help menu. Verify the endpoint is reachable.Affected if The feedback form is accessible and functional in your environment
You are affected if YouTrack is running with a version number lower than 2025.3.104432 and the feedback form functionality is accessible to users.
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 · scoped2025.3.104432
Upgrade YouTrack to version 2025.3.104432 or later. Until then, restrict access to the feedback form functionality if possible, or monitor submissions for anomalous access patterns.
2025.3.104432 or later
- 1. Back up your YouTrack database and configuration files before proceeding with the upgrade.
- 2. Download YouTrack version 2025.3.104432 or later from the official JetBrains website (www.jetbrains.com/youtrack/download).
- 3. Stop the YouTrack service on your server.
- 4. Install the new version following JetBrains standard upgrade procedures (typically by running the installer or extracting the new distribution).
- 5. Start the YouTrack service and verify the application is running correctly.
- 6. Test the feedback form functionality to ensure the application is working as expected after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64684 — 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-64684 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