CVE-2025-10554
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 Requirements in ENOVIA Product Manager from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2025x 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 confidenceStored Cross-site Scripting (XSS) vulnerability in the Requirements component of ENOVIA Product Manager allows authenticated attackers to inject malicious JavaScript code that executes in other users' browser sessions. The vulnerability affects 3DEXPERIENCE releases from R2023x through R2025x.
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>= r2023x, <= r2025xCVSS 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 Product Manager installationLocate the 3DEXPERIENCE platform installation directory and identify if the ENOVIA Product Manager module is deployed. Common paths include the 3DEXPERIENCE installation folder under /ENOVIA or /MBTools.Affected if ENOVIA Product Manager is not installed or the Requirements component is not present in the environment.
-
Determine the installed 3DEXPERIENCE versionAccess the 3DEXPERIENCE administration console or check the version.xml file in the installation directory. The version typically follows the format R2023x, R2024x, or R2025x.Affected if The installed version falls within the range R2023x through R2025x inclusive.
-
Verify the Requirements component is enabledLog into ENOVIA as an administrator and navigate to the ENOVIA Product Manager settings. Check if the Requirements module/component is enabled and accessible to users.Affected if The Requirements component is enabled and available to authenticated users in the ENOVIA interface.
-
Inspect Requirements data storage for suspicious contentQuery the ENOVIA database tables that store Requirements data (typically tables related to Requirements or RMT objects). Look for JavaScript tags, event handlers, or encoded scripts in fields that store requirement descriptions, names, or comments.Affected if Malicious script tags (script, iframe, object) or event handlers (onload, onerror, onclick) are found stored in Requirements fields.
-
Review recent Requirements creation/modification activityExamine ENOVIA audit logs or recent activity logs for the Requirements component. Look for unusual patterns in requirement entries created by users, particularly entries containing HTML or JavaScript syntax.Affected if Recent Requirements entries contain unexpected HTML tags, JavaScript keywords, or encoded payloads that were successfully stored.
A user is affected if they have ENOVIA Product Manager with the Requirements component enabled running a 3DEXPERIENCE version between R2023x and R2025x, and malicious scripts are stored in Requirements data records.
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 proper input validation and output encoding for the Requirements field, apply vendor-provided patches for affected releases, and consider Content Security Policy headers to mitigate XSS risks.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10554 — 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-10554 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