CVE-2025-35058
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) '/UserWeb/Common/MarkupServices.ashx' allows a remote, unauthenticated attacker to cause NIX to make an SMB connection to an attacker-controlled system. The attacker can capture the NTLMv2 hash of the customer-configured NIX service account.
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 confidenceNewforma Info Exchange (NIX) contains an unauthenticated vulnerability in '/UserWeb/Common/MarkupServices.ashx' that allows a remote attacker to force the NIX service to initiate an SMB connection to an attacker-controlled server. This enables capture of the NTLMv2 hash of the NIX service account through a classic SMB relay/credential harvesting attack.
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.2CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Newforma Project Center installation and versionLocate the Newforma installation directory (commonly in Program Files\Newforma\) and check the version information in the application manifest, registry key (HKLM\SOFTWARE\Newforma\ProjectCenter\Version), or the About dialog within the application.Affected if The installed version is lower than 2023.2 (e.g., 2023.1, 2022.x, or earlier).
-
Verify the vulnerable endpoint is exposedAttempt to access the URL path /UserWeb/Common/MarkupServices.ashx on the server (e.g., http://yourserver/UserWeb/Common/MarkupServices.ashx). Check if the application server responds to requests on this path.Affected if The endpoint returns any response (even an error) indicating it exists and is reachable over the network.
-
Determine if NTLM authentication is in useReview the authentication configuration for the NIX web application (typically in IIS on the server). Check the authentication providers enabled for the UserWeb application pool. Examine the web.config file for NTLM or Windows Authentication settings.Affected if NTLM authentication is enabled as an authentication provider for the web application serving the vulnerable endpoint.
-
Assess outbound network connectivity from the NIX serviceReview firewall rules and network configuration to determine if the NIX server can establish outbound TCP connections to external or untrusted systems on port 445 (SMB). Use network capture or logs to identify existing outbound SMB connections.Affected if The server is permitted to initiate outbound SMB connections to arbitrary network destinations (not just trusted internal file servers).
You are affected if Newforma Project Center version is below 2023.2, the MarkupServices.ashx endpoint is network-accessible, NTLM authentication is enabled, and the server can make outbound SMB connections to untrusted systems.
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.2
Block outbound SMB connections (TCP port 445) from the NIX server to untrusted or external networks at the firewall, or disable NTLM authentication in favor of Kerberos. Apply vendor patches when released.
Project Center 2023.2 or later
- 1. Backup the current Project Center installation and all associated databases
- 2. Download Project Center version 2023.2 or later from the official Newforma distribution portal
- 3. Stop the Project Center services and IIS application pool
- 4. Run the installer for version 2023.2
- 5. Follow the on-screen upgrade instructions, preserving configuration settings
- 6. Restart the Project Center services and IIS
- 7. Verify the /UserWeb/Common/MarkupServices.ashx endpoint no longer initiates unauthenticated SMB connections
- 8. Test that normal NIX functionality remains operational
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-35058 — 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-35058 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