CVE-2025-61803
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 · uneditedSubstance3D - Stager versions 3.1.4 and earlier are affected by an Integer Overflow or Wraparound vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
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 confidenceInteger overflow vulnerability in Substance3D Stager's file parsing logic allows arbitrary code execution when a victim opens a specially crafted malicious file. The vulnerability stems from improper integer handling during file processing, leading to memory corruption that can be leveraged for code execution in the context of the current user.
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< 3.1.5CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/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.
-
Check if Adobe Substance 3D Stager is installedLook for the application in the system program files directory, Start menu, or application launcher. On Windows, common paths include C:\Program Files\Adobe\Adobe Substance 3D Stager or C:\Program Files (x86)\Adobe\Adobe Substance 3D Stager. On macOS, check /Applications for Adobe Substance 3D Stager.appAffected if The application is present on the system
-
Determine the installed version numberRight-click the application executable or app file, select Properties, and view the Details tab for version information. Alternatively, launch the application and look for version information in the Help menu, About dialog, or welcome screenAffected if Unable to retrieve version information or version is below 3.1.5
-
Compare installed version against vulnerable rangeIf version is retrieved, check if it is less than 3.1.5. Versions such as 3.1.4, 3.1.3, 3.1.0, or any version starting with 3.0.x or 2.x are in the vulnerable rangeAffected if Installed version is 3.1.4 or any version lower than 3.1.5
The environment is affected if Adobe Substance 3D Stager is installed and the installed version is lower than 3.1.5, as the integer overflow vulnerability in file parsing can be triggered when opening specially crafted files.
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.
dbcve · scoped3.1.5
Update Substance3D Stager to a version newer than 3.1.4. Until patched, avoid opening files from untrusted sources.
3.1.5 or later
- 1. Verify the current version of Substance 3D Stager by opening the application and checking Help > About Substance 3D Stager
- 2. Navigate to the official Adobe download page at helpx.adobe.com or the Substance 3D Stager product page
- 3. Download Substance 3D Stager version 3.1.5 or later
- 4. Close the current instance of Substance 3D Stager if it is running
- 5. Run the downloaded installer and follow the on-screen prompts to complete the upgrade
- 6. After installation, verify the version has been updated to 3.1.5 or later via Help > About Substance 3D Stager
- 7. Exercise caution when opening files from untrusted sources to mitigate social engineering aspects of this vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61803 — 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-61803 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