# CVE-2025-3984: Apereo CAS Groovy Code RegisteredServiceSimpleFormController.java saveService code injection

> Remote attackers with permissions can execute arbitrary code via Groovy injection in the saveService function of Apereo CAS.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Apr 2025
- **Updated:** 28 Apr 2025
- **Also known as:** GHSA-37pq-893f-g7q5

## What is CVE-2025-3984?

CVE-2025-3984 is a low-severity code injection vulnerability in Apereo CAS, published on 27 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in Apereo CAS 5.2.6 and classified as critical. Affected by this issue is the function saveService of the file cas-5.2.6\webapp-mgmt\cas-management-webapp-support\src\main\java\org\apereo\cas\mgmt\services\web\RegisteredServiceSimpleFormController.java of the component Groovy Code Handler. The manipulation leads to code injection. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2025-3984?

2 open source packages ship an affected version, including org.apereo.cas:cas-management-webapp-support. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apereo.cas:cas-management-webapp-support` | Maven | All versions to 5.2.6 | None |
| `org.apereo.cas:cas-management-webapp-support` | Maven | All versions to 5.2.6 | None |

Products: Apereo Central Authentication Service.

## How do I fix CVE-2025-3984?

No fix has been published for CVE-2025-3984 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-3984 being exploited?

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

## Other vulnerabilities in Apereo CAS

- [CVE-2023-4612](https://insights.sbomify.com/CVE-2023-4612/): MFA bypass in Apereo CAS (critical 9.8)
- [CVE-2024-4399](https://insights.sbomify.com/CVE-2024-4399/): CAS <= 1.0.0 - Unauthenticated SSRF (critical 9.1)
- [CVE-2019-10754](https://insights.sbomify.com/CVE-2019-10754/): Use of Insufficiently Random Values in Apereo CAS (high 8.1)
- [CVE-2020-27178](https://insights.sbomify.com/CVE-2020-27178/): Improper Authentication in Apereo CAS (high 7.5)
- [CVE-2015-1169](https://insights.sbomify.com/CVE-2015-1169/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3984 and fix it if it is affected.

What it is: CVE-2025-3984 is a low-severity code injection vulnerability in Apereo CAS, published on 27 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3984 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apereo.cas:cas-management-webapp-support (Maven): affected all versions up to 5.2.6; no fix listed
- org.apereo.cas:cas-management-webapp-support (Maven): affected all versions up to 5.2.6; no fix listed

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-2025-3984/ (Markdown: https://insights.sbomify.com/CVE-2025-3984/index.md)
```

## Sources

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

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