# CVE-2025-0707: Rise Group Rise Mode Temp CPU Startup CRYPTBASE.dll untrusted search path

> Local attackers can exploit an untrusted search path in CRYPTBASE.dll to execute arbitrary code in Rise Mode Temp CPU.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-h95h-q9r2-fmg8

## What is CVE-2025-0707?

CVE-2025-0707 is a high-severity vulnerability in Rise Mode Temp CPU, published on 24 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in Rise Group Rise Mode Temp CPU 2.1. It has been classified as critical. This affects an unknown part in the library CRYPTBASE.dll of the component Startup. The manipulation leads to untrusted search path. The attack needs to be approached locally.

Weakness: CWE-426 (Untrusted Search Path)

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


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

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

## Is CVE-2025-0707 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0707 is a high-severity vulnerability in Rise Mode Temp CPU, published on 24 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0707 in the wild and no public exploit code.

Affected product: Rise Mode Temp CPU. 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-0707/ (Markdown: https://insights.sbomify.com/CVE-2025-0707/index.md)
```

## Sources

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

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