# CVE-2025-12626: jeecgboot jeewx-boot WxActGoldeneggsPrizesController.java getImgUrl path traversal

> Attackers can exploit a path traversal vulnerability in the getImgUrl function to read arbitrary files from the server.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 3 Nov 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-rw86-f997-g9mx

## What is CVE-2025-12626?

CVE-2025-12626 is a medium-severity path traversal vulnerability in jeecgboot jeewx-boot, published on 3 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security flaw has been discovered in jeecgboot jeewx-boot up to 641ab52c3e1845fec39996d7794c33fb40dad1dd. This affects the function getImgUrl of the file WxActGoldeneggsPrizesController.java. Performing manipulation of the argument imgurl results in path traversal. Remote exploitation of the attack is possible. The exploit has been released to the public and may be exploited. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The root cause was initially fixed but can be evaded with additional encoding.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2025-12626 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12626 is a medium-severity path traversal vulnerability in jeecgboot jeewx-boot, published on 3 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12626 exists.

Affected product: jeecgboot jeewx-boot. 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-12626/ (Markdown: https://insights.sbomify.com/CVE-2025-12626/index.md)
```

## Sources

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

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