Command Injection in tomato
Priority LOW 38CWE-77Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Code execution
- Confidentiality · integrity · availability
- —
- Fix status
- No fix listed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-77.
Summary
All versions of `tomato` are vulnerable to Command Injection. The /api/exec endpoint does not validate user input allowing attackers to run arbitrary commands in the system. ## Recommendation No fix is currently available. Consider using an alternative module until a fix is made available.
Why it matters now
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | tomato (npm) | all versions | — | No fix listed | GHSA-wqhw-frpx-5mmp |
- tomato (npm) Vendor— Affected all versions Fixed in — No fix listed GHSA-wqhw-frpx-5mmp
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-wqhw-frpx-5mmp
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences