dbcve.org
Project CenterApplication · Newforma

CVE-2025-35056

MEDIUM · 5.0 CVSS v3.1 Published 2025-10-09
Fix available
A fix is available. Upgrade to 2024.1 or later.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Newforma Info Exchange (NIX) '/UserWeb/Common/MarkupServices.ashx' 'StreamStampImage' accepts an encrypted file path and returns an image of the specified file. An authenticated attacker can read arbitrary files subject to the privileges of NIX, typically 'NT AUTHORITY\NetworkService', and the ability of StreamStampImage to process the file. The encrypted file path can be generated using the shared, hard-coded secret key described in CVE-2025-35052. This vulnerability cannot be exploited as an 'anonymous' user as described in CVE-2025-35062.

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 confidence

Newforma Info Exchange (NIX) contains an authenticated arbitrary file read vulnerability in the StreamStampImage function of MarkupServices.ashx. The endpoint accepts encrypted file paths using a hard-coded shared secret key (CVE-2025-35052), allowing authenticated attackers to read arbitrary files on the system subject to the NetworkService account privileges.

MitigationRemediate by rotating the compromised hard-coded encryption key, implementing proper path validation to prevent directory traversal, and implementing proper authorization checks. Update to patched versions when available.

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
Project CenterApplication
Affected:< 2024.1

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
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Newforma Project Center version
    Locate the installed Newforma Project Center application and retrieve its version number from the program files, installation directory, or Windows registry under the application entry.
    Affected if The installed version is lower than 2024.1 (e.g., 2023.x, earlier versions).
  2. Locate the MarkupServices.ashx endpoint
    Search the web application directory for the file MarkupServices.ashx, typically found in the NIX web application's bin or root folder.
    Affected if The file MarkupServices.ashx exists in the web application deployment.
  3. Verify the hard-coded shared secret key exists
    Inspect the configuration files or assemblies associated with the NIX web application for the hard-coded encryption key referenced in CVE-2025-35052.
    Affected if A hard-coded static encryption key is present in the application configuration or code.
  4. Review web server logs for MarkupServices.ashx access
    Examine web server access logs for requests to MarkupServices.ashx, particularly those involving the StreamStampImage function parameter.
    Affected if There are authenticated requests to StreamStampImage with encoded file path parameters.

A user is affected if Newforma Project Center version is below 2024.1, the MarkupServices.ashx endpoint with StreamStampImage function is exposed, and the hard-coded shared secret key remains in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2024.1 or later
Fixed in 2024.1
Interim mitigation

Remediate by rotating the compromised hard-coded encryption key, implementing proper path validation to prevent directory traversal, and implementing proper authorization checks. Update to patched versions when available.

Recommended fix Moderate confidence

2024.1

  1. Verify current Newforma Project Center version installed in the environment
  2. Schedule a maintenance window for the upgrade process
  3. Obtain the Newforma Project Center 2024.1 installation package from official Newforma distribution channels
  4. Back up the existing Newforma database and configuration files
  5. Run the installer for version 2024.1 following Newforma's standard upgrade documentation
  6. Verify the upgrade completed successfully by checking the version number in the application
  7. Test that the '/UserWeb/Common/MarkupServices.ashx' endpoint functions correctly with proper authentication
  8. Confirm the path traversal vulnerability is remediated by verifying arbitrary file access is no longer possible
Caveat Review Newforma 2024.1 release notes for any feature changes or configuration adjustments that may affect existing workflows

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Project Center Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-35056 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-35056 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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