CVE-2025-63665
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 issue in GT Edge AI Community Edition Versions before v2.0.12 allows attackers to execute arbitrary code via injecting a crafted JSON payload into the Prompt window.
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 confidenceGT Edge AI Community Edition versions before v2.0.12 contains a code injection vulnerability in the Prompt window functionality. Attackers can execute arbitrary code by submitting a crafted JSON payload, achieving remote code execution due to insufficient input validation.
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< 2.0.12CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 the installed GT Edge AI versionCheck the application's About dialog, Help menu, or look for version files in the installation directory. Compare the version number to the vulnerable range: versions before v2.0.12 are affected.Affected if The installed version is lower than 2.0.12 (e.g., 2.0.11, 2.0.10, etc.)
-
Confirm the Prompt window feature is accessibleLocate the Prompt window functionality in the GT Edge AI interface. This is the vulnerable component where JSON payloads can be submitted.Affected if The Prompt window feature is present and accessible in the application UI
-
Review application logs for suspicious JSON inputExamine GT Edge AI log files for entries containing unusual JSON structures or code-like strings submitted through the Prompt window. Look for patterns that may indicate exploitation attempts.Affected if Log entries show unexpected JSON payloads or code execution patterns in Prompt window requests
-
Check for unexpected system behavior or artifactsInvestigate if any unexpected processes, scripts, or files were created on the system that correlate with GT Edge AI usage, especially around the time of Prompt window interactions.Affected if Unusual system changes or unauthorized script executions are observed that coincide with GT Edge AI Prompt window usage
A user is affected if GT Edge AI Community Edition is installed at a version lower than 2.0.12 and the Prompt window feature has been used, as this combination allows the code injection vulnerability to be exploited.
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 · scoped2.0.12
Upgrade to GT Edge AI Community Edition v2.0.12 or later to obtain the security patch that addresses this vulnerability.
GT Edge AI Community Edition v2.0.12
- 1. Back up the current GT Edge AI installation and configuration data
- 2. Download GT Edge AI Community Edition v2.0.12 from the official vendor source
- 3. Stop the GT Edge AI service or application
- 4. Install version 2.0.12 following the vendor's standard upgrade procedure
- 5. Verify the installation completed successfully
- 6. Restart the GT Edge AI service
- 7. Test that the Prompt window functionality works correctly with normal JSON inputs
- 8. Confirm the vulnerability is remediated by verifying arbitrary code cannot be injected via JSON payloads
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-63665 — 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-63665 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