CVE-2025-35062
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 · uneditedNewforma Info Exchange (NIX) before version 2023.1 by default allows anonymous authentication which allows an unauthenticated attacker to exploit additional vulnerabilities that require authentication.
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 confidenceNewforma Info Exchange (NIX) versions prior to 2023.1 ship with anonymous authentication enabled by default, allowing unauthenticated remote attackers to access functionality that should require authentication and potentially chain with other vulnerabilities that mandate authenticated sessions.
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< 2023.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Identify Newforma Project Center versionOpen Windows Control Panel > Programs and Features, or check the application installation directory for the installed version of Newforma Project CenterAffected if The installed version is prior to 2023.1 (e.g., 2022.x, 2021.x, etc.)
-
Confirm Newforma Info Exchange (NIX) component is presentVerify that the Newforma Info Exchange component is installed alongside Project Center, typically found in the same installation directory or listed as a component in Programs and FeaturesAffected if NIX is installed and the version is prior to 2023.1
-
Check anonymous authentication statusExamine the NIX application configuration files or administrative settings for the authentication configuration; look for settings related to anonymous or unauthenticated accessAffected if Anonymous authentication is enabled (this is the default state in versions prior to 2023.1)
You are affected if Newforma Project Center with the NIX component is installed at a version prior to 2023.1, as these versions ship with anonymous authentication enabled by default.
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 · scoped2023.1
Upgrade to NIX version 2023.1 or later, or disable anonymous authentication in the application configuration to enforce proper authentication requirements.
2023.1
- Identify current Newforma Info Exchange (NIX) / Project Center version
- Backup all configuration files, databases, and critical data
- Obtain Newforma Info Exchange version 2023.1 or later from the official vendor
- Install or apply the upgrade to version 2023.1
- Verify that anonymous authentication is no longer enabled by default after upgrade
- Confirm the application functions normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-35062 — 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-35062 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