dbcve.org
Project CenterApplication · Newforma

CVE-2025-35052

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-09
Fix available
A fix is available. Upgrade to after 2024.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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) uses a hard-coded key to encrypt certain query parameters. Some encrypted parameter values can specify paths to download files, potentially bypassing authentication and authorization, for example, the 'qs' parameter used in '/DownloadWeb/download.aspx'. This key is shared across NIX installations. NIX 2023.3 and 2024.1 limit the use of hard-coded keys.

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) uses a hard-coded cryptographic key to encrypt query parameters, including the 'qs' parameter in /DownloadWeb/download.aspx. Encrypted parameter values can specify file paths for download, potentially bypassing authentication and authorization. The hard-coded key is identical across all NIX installations, creating a systemic vulnerability.

MitigationUpgrade to NIX 2023.3 or 2024.1 which limits hard-coded key usage, or apply subsequent vendor patches. Conduct a thorough review to ensure all hard-coded keys have been eliminated and implement dynamic key management.

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.3

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 installation and version
    Locate the Newforma Project Center installation directory or check the installed programs/features on the server. Look for version information in the application metadata, installation logs, or program files.
    Affected if The installed version is 2024.3 or any version lower than 2024.3
  2. Confirm NIX web components are present
    Check if the Info Exchange (NIX) web application is deployed by looking for the /DownloadWeb/ directory in the web server's document root or application directory. Verify that download.aspx exists.
    Affected if The NIX web components with download.aspx are present and accessible
  3. Inspect application configuration for hard-coded keys
    Search configuration files within the NIX application directory for cryptographic keys, encryption keys, or secret values. Look in web.config, app.config, or similar configuration files for hard-coded values used for encryption or signing.
    Affected if A hard-coded cryptographic key is found in configuration files that is identical across installations
  4. Verify qs parameter encryption usage
    Examine the application's handling of the 'qs' query parameter in /DownloadWeb/download.aspx. Determine if parameters are encrypted using a static key rather than dynamically generated or per-instance keys.
    Affected if The 'qs' parameter is encrypted using a static, hard-coded key that is consistent across all installations

A user is affected if Newforma Project Center version 2024.3 or lower is installed, the NIX web interface is accessible, and a hard-coded cryptographic key is used to encrypt the 'qs' parameter in download.aspx.

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 a release after 2024.3
Interim mitigation

Upgrade to NIX 2023.3 or 2024.1 which limits hard-coded key usage, or apply subsequent vendor patches. Conduct a thorough review to ensure all hard-coded keys have been eliminated and implement dynamic key management.

Recommended fix Moderate confidence

Newforma Project Center 2024.4 or later (contact vendor for exact fixed release)

  1. Identify the current Newforma Project Center version in use
  2. Contact Newforma technical support to confirm the specific version that addresses CVE-2025-35052
  3. Upgrade the Newforma Project Center installation to the latest stable release that includes the fix for the hardcoded cryptographic key vulnerability
  4. After upgrade, verify that the '/DownloadWeb/download.aspx' endpoint no longer allows unauthenticated file access via encrypted 'qs' parameter
  5. If direct upgrade is not immediately possible, restrict network access to the '/DownloadWeb/download.aspx' endpoint as a temporary mitigation
Caveat Review Newforma release notes for your specific upgrade path as custom configurations or integrations may require adjustment

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

Fix this in Project Center Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-35052 — 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-35052 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