CVE-2025-66687
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 · uneditedDoom Launcher 3.8.1.0 is vulnerable to Directory Traversal due to missing file path validation during the extraction of game files
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 · moderate confidenceDoom Launcher 3.8.1.0 contains a directory traversal vulnerability during game file extraction. The application fails to validate file paths within extracted archives, allowing attackers to use path traversal sequences (e.g., '../') to write files outside the intended target directory. This could enable arbitrary file write and potentially remote code execution depending on write location.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Identify Doom Launcher versionLocate the Doom Launcher executable (commonly in Program Files or a custom install directory) and check its version properties, or run: right-click the executable > Properties > Details to view File VersionAffected if The version displayed is 3.8.1.0 specifically
-
Verify game file extraction feature existsCheck if Doom Launcher has an option to extract game files from archives (look for import, extract, or load game from archive functionality in the application UI or documentation)Affected if The application includes game file extraction capability and it has been used to load game archives
-
Inspect extraction output logs or directoriesReview the directory where extracted game files are stored (typically a 'games', 'extracted', or user-defined folder within the Doom Launcher directory) and check if any extracted files appear outside the intended target folderAffected if Files exist outside the designated extraction directory, or logs show path traversal sequences like '../' in file paths
-
Check for recent extraction activityExamine the application logs, temp directories, or Doom Launcher working directory for recent extraction operations and their output pathsAffected if Recent extraction operations wrote files to locations inconsistent with the intended extraction target directory
A user is affected if they run Doom Launcher version 3.8.1.0 and have used the game file extraction feature, since the lack of path validation allows archives to write files outside the intended directory via path traversal sequences.
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 dataImplement strict path validation during archive extraction to ensure all extracted files remain within the designated extraction directory. Reject any archive entries containing path traversal sequences or absolute paths.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66687 — 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-66687 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