CVE-2025-9976
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 OS Command Injection vulnerability affecting Station Launcher App in 3DEXPERIENCE platform from Release 3DEXPERIENCE R2022x through Release 3DEXPERIENCE R2025x could allow an attacker to execute arbitrary code on the user's machine.
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 confidenceAn OS Command Injection vulnerability exists in the Station Launcher App component of the 3DEXPERIENCE platform spanning versions R2022x through R2025x. Attackers can inject malicious OS commands through unsanitized input in the launcher, leading to arbitrary code execution on the victim's machine.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
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 3DEXPERIENCE platform installationSearch for 3DEXPERIENCE installation directories or check installed programs list for '3DEXPERIENCE' or 'Dassault Systèmes' entriesAffected if 3DEXPERIENCE platform is installed on the system
-
Identify installed versionLocate version information in installation folder (typically contains R2022x, R2023x, R2024x, or R2025x in path or version file) or check program version detailsAffected if Installed version falls within R2022x through R2025x range
-
Verify Station Launcher App component presenceCheck for 'Station Launcher' or ' launcher' executables or services within the 3DEXPERIENCE installation directoryAffected if Station Launcher App component is present on the system
-
Assess launcher execution contextReview how Station Launcher is invoked - check for shortcut properties, startup configurations, or integration with other applicationsAffected if Station Launcher is configured to run automatically or processes external input
-
Verify input handling configurationInspect launcher configuration files or logs for any user-controlled input pathways that could reach OS command executionAffected if Launcher accepts external input without sanitization or validation
If 3DEXPERIENCE R2022x through R2025x is installed with the Station Launcher App component active, the environment is likely affected by this OS command injection vulnerability.
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 dataApply the vendor-issued patch for affected 3DEXPERIENCE releases (R2022x through R2025x) as soon as possible. Prioritize deployment given the critical severity (CVSS 9) and the availability of public exploitation potential.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9976 — 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-9976 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