CVE-2025-0828
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 · uneditedA stored Cross-site Scripting (XSS) vulnerability affecting Engineering Release in ENOVIA Product Engineering Specialist from Release 3DEXPERIENCE R2022x through Release 3DEXPERIENCE R2024x allows an attacker to execute arbitrary script code in user's browser session.
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 confidenceA stored Cross-site Scripting (XSS) vulnerability in the Engineering Release component of ENOVIA Product Engineering Specialist (3DEXPERIENCE R2022x through R2024x) allows authenticated attackers to inject malicious JavaScript that executes in other users' browser sessions when viewing compromised content.
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>= r2022x, <= r2024xCVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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.
-
Identify ENOVIA/3DEXPERIENCE installationLocate the 3DEXPERIENCE installation directory or check system inventory for ENOVIA Product Engineering Specialist components. Common installation paths include C:\3DS on Windows or /home/3ds on Linux.Affected if ENOVIA Product Engineering Specialist is not installed - not affected.
-
Determine installed 3DEXPERIENCE versionAccess the 3DEXPERIENCE administration console or check version files in the installation directory. The version typically appears in the format r2022x, r2023x, or r2024x in about/version information.Affected if Version is earlier than r2022x or later than r2024x - not affected.
-
Verify Engineering Release module is enabledCheck the ENOVIA application configuration or administration settings to confirm whether the Engineering Release component is active. This may be viewable through the 3DEXPERIENCE Platform Services or ENOVIA administration interface.Affected if Engineering Release module is not enabled or not present - not affected.
-
Inspect Engineering Release data for suspicious contentQuery the ENOVIA database or use the Engineering Release interface to review stored release records, comments, descriptions, or attachment metadata for unusual script tags, javascript: URIs, or event handler attributes.Affected if Malicious script payloads are found in Engineering Release records - potentially affected and exploited.
User is affected if 3DEXPERIENCE ENOVIA with Engineering Release module is installed and the version falls within r2022x through r2024x, especially if unauthorized script content is discovered in Engineering Release data.
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 patch for CVE-2025-0828; until available, sanitize user-supplied input in the Engineering Release module and implement Content Security Policy (CSP) headers to mitigate script execution risks.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0828 — 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-0828 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