# CVE-2020-25802: Authenticated attackers with developer privileges in Crafter Studio may execute OS commands via Groovy scripting.

> Authenticated developers can execute arbitrary OS commands via Groovy scripting in Crafter Studio, requiring an upgrade to patched versions.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Oct 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-wq3v-3grq-6f86

## What is CVE-2020-25802?

CVE-2020-25802 is a medium-severity code injection vulnerability in Crafter CMS, published on 6 Oct 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Improper Control of Dynamically-Managed Code Resources vulnerability in Crafter Studio of Crafter CMS allows authenticated developers to execute OS commands via Groovy scripting. This issue affects: Crafter Software Crafter CMS 3.0 versions prior to 3.0.27; 3.1 versions prior to 3.1.7.

Weakness: CWE-913 (Improper Control of Dynamically-Managed Code Resources)

## Which versions are affected by CVE-2020-25802?

4 open source packages ship an affected version, including org.craftercms:crafter-studio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.craftercms:crafter-studio` | Maven | From 3.0 | 3.0.27 |
| `org.craftercms:crafter-studio` | Maven | From 3.0 | 3.0.27 |
| `org.craftercms:crafter-studio` | Maven | From 3.1 | 3.1.7 |
| `org.craftercms:crafter-studio` | Maven | From 3.1 | 3.1.7 |

Products: Craftercms Studio.

## How do I fix CVE-2020-25802?

Upgrade org.craftercms:crafter-studio to a fixed version for your release line: 3.0.27 or 3.1.7.

## Is CVE-2020-25802 being exploited?

There is no known exploitation of CVE-2020-25802 in the wild and no public exploit code.

## Other vulnerabilities in Crafter CMS

- [CVE-2020-25803](https://insights.sbomify.com/CVE-2020-25803/): Improper Control of Dynamically-Managed Code Resources in Crafter CMS Crafter Studio (medium 4.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25802 and fix it if it is affected.

What it is: CVE-2020-25802 is a medium-severity code injection vulnerability in Crafter CMS, published on 6 Oct 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-25802 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.craftercms:crafter-studio (Maven): affected from 3.0; fixed in 3.0.27
- org.craftercms:crafter-studio (Maven): affected from 3.0; fixed in 3.0.27
- org.craftercms:crafter-studio (Maven): affected from 3.1; fixed in 3.1.7
- org.craftercms:crafter-studio (Maven): affected from 3.1; fixed in 3.1.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-25802/ (Markdown: https://insights.sbomify.com/CVE-2020-25802/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-25802
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-25802
- OSV: https://osv.dev/vulnerability/CVE-2020-25802

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-25802/
Summaries are generated and may contain mistakes; the official description above is the record.