# CVE-2025-65885: Command injection in n/a

> Local attackers can execute arbitrary code by injecting startup scripts via crafted text files in the Data directory of Delight Custom Firmware for Symbian devices.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Dec 2025
- **Updated:** 26 Dec 2025
- **Also known as:** GHSA-chq3-v87j-fwq5

## What is CVE-2025-65885?

CVE-2025-65885 is a medium-severity command injection vulnerability in n/a, published on 26 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in the Delight Custom Firmware (CFW) for Nokia Symbian Belle devices on Nokia 808 (Delight v1.8), Nokia N8 (Delight v6.7), Nokia E7 (Delight v1.3), Nokia C7 (Delight v6.7), Nokia 700 (Delight v1.2), Nokia 701 (Delight v1.1), Nokia 603 (Delight v1.0), Nokia 500 (Delight v1.2), Nokia E6 (Delight v1.0), Nokia Oro (Delight v1.0), and Vertu Constellation T (Delight v1.0) allowing local attackers to inject startup scripts via crafted .txt files in the :\Data directory.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Symwld Delight Custom Firmware.

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

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

## Is CVE-2025-65885 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65885 is a medium-severity command injection vulnerability in n/a, published on 26 Dec 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-65885 in the wild and no public exploit code.

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

## Sources

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

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