# CVE-2025-63690: Code injection in n/a

> Attackers can execute arbitrary commands via reflection in Quartz scheduled tasks, leading to remote code execution in pig-mesh Pig.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2025
- **Updated:** 7 Nov 2025
- **Also known as:** GHSA-59mx-mhm6-4342

## What is CVE-2025-63690?

CVE-2025-63690 is a critical code injection vulnerability in n/a, published on 7 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In pig-mesh Pig versions 3.8.2 and below, when setting up scheduled tasks in the Quartz management function under the system management module, it is possible to execute any Java class with a parameterless constructor and its methods with parameter type String through reflection. At this time, the eval method in Tomcat's built-in class jakarta.el.ELProcessor can be used to execute commands, leading to a remote code execution vulnerability.

Weakness: CWE-470 (Use of Externally-Controlled Input to Select Classes or Code)

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

It affects 1 product.


Products: Pig4cloud Pig.

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

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

## Is CVE-2025-63690 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63690 exists.

## Other vulnerabilities in n/a

- [CVE-2025-63691](https://insights.sbomify.com/CVE-2025-63691/): Missing authorization in n/a (critical 9.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63690 is a critical code injection vulnerability in n/a, published on 7 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63690 exists.

Affected product: n/a. 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-63690/ (Markdown: https://insights.sbomify.com/CVE-2025-63690/index.md)
```

## Sources

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

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