# CVE-2025-12140: RCE in Wirtualna Uczelnia

> An unauthenticated attacker can execute arbitrary code via insecure Java expression processing in the redirect mechanism.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Nov 2025
- **Updated:** 28 Nov 2025
- **Also known as:** GHSA-4cgm-43x9-f8f3

## What is CVE-2025-12140?

CVE-2025-12140 is a critical code injection vulnerability in Simple SA Wirtualna Uczelnia, published on 27 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The application contains an insecure 'redirectToUrl' mechanism that incorrectly processes the value of the 'redirectUrlParameter' parameter. The application interprets the entered string of characters as a Java expression, allowing an unauthenticated attacer to perform arbitrary code execution.
This issue was fixed in version wu#2016.1.5513#0#20251014_113353

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

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


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

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

## Is CVE-2025-12140 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12140 is a critical code injection vulnerability in Simple SA Wirtualna Uczelnia, published on 27 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12140 in the wild and no public exploit code.

Affected product: Simple SA Wirtualna Uczelnia. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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