CVE-2025-65885
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceLocal attackers can inject arbitrary startup scripts via crafted .txt files placed in the :\Data directory of Delight Custom Firmware for Nokia Symbian Belle devices. This allows code execution at device startup with elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.8= 6.7= 1.3= 1.1= 1.2= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Delight Custom Firmware is installedIdentify the device firmware by checking system information or boot sequence for 'Delight Custom Firmware' or 'Symwld' branding on the Nokia Symbian Belle deviceAffected if The device is running Delight Custom Firmware rather than stock Nokia firmware
-
Check the firmware versionRetrieve the firmware version from the device settings or system information panelAffected if The installed version matches 1.8, 6.7, 1.3, 1.1, 1.2, or 1.0
-
Examine the Data directory for txt filesAccess the :\Data directory on the device filesystem and list all .txt files presentAffected if Unexpected or unrecognized .txt files exist in the :\Data directory that were not personally created by the user
-
Inspect txt file contentsOpen and review the contents of any .txt files found in :\Data for suspicious script commands or unfamiliar codeAffected if Any .txt file contains startup script commands, shell instructions, or code not authored by the legitimate device user
-
Verify physical access exposureDetermine whether the device can be accessed physically by unauthorized individuals to place files on the storageAffected if The device is in a location where untrusted parties could physically access it and modify files on the storage
The device is affected if it runs Delight Custom Firmware versions 1.8, 6.7, 1.3, 1.1, 1.2, or 1.0 on Nokia Symbian Belle and has unauthorized .txt files in the :\Data directory.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince Delight Custom Firmware is abandoned and no vendor patches exist, physical security of affected devices is the primary mitigation; users should avoid using this custom firmware on production devices.
- Consultation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65885 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-65885 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data