Build server command execution via postinstall scripts
Published Mar 1, 2025 · Updated Mar 4, 2025
Code injection in ToDesktop for Electron before 2024-10-03 allows remote authenticated users to execute commands on its build server. The hosted builder executes an application's package.json postinstall script inside an overprivileged container able to read full-scope Firebase credentials. A ToDesktop account and submitted application are required; exploitation exposes platform secrets and enables unauthorized updates to hosted apps.
Summary
What happened
Code injection in ToDesktop for Electron before 2024-10-03 allows remote authenticated users to execute commands on its build server. The hosted builder executes an application's package.json postinstall script inside an overprivileged container able to read full-scope Firebase credentials. A ToDesktop account and submitted application are required; exploitation exposes platform secrets and enables unauthorized updates to hosted apps.
The record
- CVE
- CVE-2025-27554
- Published
- Mar 1, 2025
- Updated
- Mar 4, 2025
- Vendor
- ToDesktop
- Product
- ToDesktop Builder
- Classifications
- CWE-94, T1195.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 1, 2025CVE publishedPublication date reported by the CVE source.
- Mar 4, 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=0 <2024-10-03
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
- ToDesktop deployment-pipeline proof of conceptproof of concept · 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