dbcve.org
Project CenterApplication · Newforma

CVE-2025-35054

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 →
55/100
Remediation priority · Elevated
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) stores credentials used to configure NPCS in 'HKLM\Software\WOW6432Node\Newforma\<version>\Credentials'. The credentials are encrypted but the encryption key is stored in the same registry location. Authenticated users can access both the credentials and the encryption key. If these are Active Directory credentials, an attacker may be able to gain access to additional systems and resources.

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) stores NPCS configuration credentials in the Windows registry at HKLM\Software\WOW6432Node\Newforma\<version>\Credentials. While the credentials are encrypted, the encryption key is stored in the same registry location, allowing authenticated users to access both the encrypted credentials and the decryption key, potentially exposing Active Directory credentials.

MitigationReplace the current credential storage mechanism with Windows Data Protection API (DPAPI) or Windows Credential Manager to securely store credentials separately from the encryption key, ensuring only privileged system accounts can access decryption materials.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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. Confirm Newforma Project Center installation
    Check for Newforma Project Center in Add/Remove Programs (appwiz.cpl) or look for installation directory under C:\Program Files\Newforma
    Affected if Newforma Project Center is installed and version is 2024.3 or lower
  2. Identify installed Newforma version
    Check registry key HKLM\Software\WOW6432Node\Newforma\ for subkeys containing version numbers, or right-click on Newforma executable and view Properties > Details for version info
    Affected if Installed version is 2024.3 or lower (any version <= 2024.3)
  3. Verify credential registry location exists
    Open regedit and navigate to HKLM\Software\WOW6432Node\Newforma\<version>\Credentials (where <version> is your installed version), check if this key exists
    Affected if The Credentials subkey exists under the Newforma version registry path
  4. Check for encryption key in same location
    Within the HKLM\Software\WOW6432Node\Newforma\<version>\Credentials registry key, examine values for any encryption key, key material, or cryptographic seed data stored alongside credential blobs
    Affected if Encryption key or key material is present in the same registry location as stored credentials

User is affected if Newforma Project Center version 2024.3 or lower is installed and credentials with an encryption key are both stored in the registry path HKLM\Software\WOW6432Node\Newforma\<version>\Credentials.

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

Replace the current credential storage mechanism with Windows Data Protection API (DPAPI) or Windows Credential Manager to securely store credentials separately from the encryption key, ensuring only privileged system accounts can access decryption materials.

Recommended fix Moderate confidence

Project Center > 2024.3 (e.g., 2024.4 or latest stable release)

  1. Identify the current installed version of Newforma Project Center
  2. Contact Newforma support or check their official release notes to obtain the latest version that addresses CVE-2025-35054
  3. Upgrade Project Center to a version newer than 2024.3 (such as 2024.4 or later if available)
  4. After upgrading, verify that credentials are no longer stored in the registry location HKLM\Software\WOW6432Node\Newforma\<version>\Credentials
  5. Alternatively, contact Newforma to confirm if a patch is available for your current version
Caveat Review release notes for any configuration or workflow changes between your current version and the target version

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

Fix this in Project Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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