Authenticated OS command execution via Groovy sandbox bypass
Published Feb 2, 2026 · Updated Feb 2, 2026
Code injection in Crafter Studio before 4.5.0 allows remote authenticated users with developer access to execute OS commands. The Groovy sandbox fails to reject crafted constructs using AST transformations, expression parsers, and object factories that reach command-capable Java APIs. Developer-level Studio or site-repository access is required; successful exploitation runs commands with the server process's privileges.
Summary
What happened
Code injection in Crafter Studio before 4.5.0 allows remote authenticated users with developer access to execute OS commands. The Groovy sandbox fails to reject crafted constructs using AST transformations, expression parsers, and object factories that reach command-capable Java APIs. Developer-level Studio or site-repository access is required; successful exploitation runs commands with the server process's privileges.
The record
- CVE
- CVE-2026-1770
- Published
- Feb 2, 2026
- Updated
- Feb 2, 2026
- Vendor
- Crafter Software Corporation
- Product
- CrafterCMS
- Classifications
- CWE-913, CAPEC-253, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 2, 2026CVE publishedPublication date reported by the CVE source.
- Feb 2, 2026Record 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=4.0.0 <4.5.0
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
- Groovy Sandbox Bypass proof-of-concept collectionproof 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