CVE-2025-10553
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 Factory Resource Management in DELMIA Factory Resource 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 XSS in DELMIA Factory Resource Manager's Factory Resource Management component allows attackers to inject malicious JavaScript through user-supplied input that gets stored in the application database and executed in victims' browser sessions when viewing the compromised data.
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 installed 3ds 3dexperience versionUse the 3dexperience version checker or licensing utility to determine the exact release version (e.g., r2023x, r2024x, r2025x)Affected if the version falls within r2023x through r2025x inclusive
-
Confirm Factory Resource Manager module is activeCheck if the Factory Resource Management component is licensed and enabled in the 3dexperience platform services or session managerAffected if the Factory Resource Manager module is installed and accessible to users
-
Identify user input points in Factory Resource ManagementNavigate to the Factory Resource Management interface and locate all data entry forms, parameter fields, or import functions that accept user-supplied contentAffected if the component accepts user input that gets persisted to the database
-
Verify if stored data is rendered without encodingSubmit a test payload with HTML/JavaScript characters (e.g., <script>alert(1)</script>) through a Factory Resource Management input field, then view the stored record to see if the script executesAffected if the injected script executes in the browser when viewing the stored data, indicating lack of output encoding
-
Review application logs for XSS attack indicatorsSearch application and web server logs for patterns containing script tags, javascript: URIs, or event handler attributes in Factory Resource Management data storageAffected if log entries show malicious script payloads stored in the database
You are affected if you run 3ds 3dexperience versions r2023x through r2025x and have the Factory Resource Management module enabled with user input fields that accept and display data without proper encoding.
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 context-aware output encoding and input validation/sanitization on all user-supplied data entering the Factory Resource Management module; apply Content Security Policy headers to mitigate XSS execution.
- Consultation6.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10553 — 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-10553 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