Code execution via unescaped custom URL data
Published Aug 11, 2025 · Updated Aug 11, 2025
Code injection in Cherry Studio 1.4.8 through 1.5.0 allows remote attackers to execute code through a crafted custom URL. The provider URL handler interpolates attacker-controlled data into Electron executeJavaScript, allowing injected renderer code to call exposed file and shell IPC services. Exploitation requires a user to approve opening the cherrystudio:// link, after which code runs with the application user's privileges.
Summary
What happened
Code injection in Cherry Studio 1.4.8 through 1.5.0 allows remote attackers to execute code through a crafted custom URL. The provider URL handler interpolates attacker-controlled data into Electron executeJavaScript, allowing injected renderer code to call exposed file and shell IPC services. Exploitation requires a user to approve opening the cherrystudio:// link, after which code runs with the application user's privileges.
The record
- CVE
- CVE-2025-54063
- Published
- Aug 11, 2025
- Updated
- Aug 11, 2025
- Vendor
- CherryHQ
- Product
- Cherry Studio
- Classifications
- CWE-94, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2025CVE publishedPublication date reported by the CVE source.
- Aug 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.4.8, < 1.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory custom-URL proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo