dbcve.org
Project CenterApplication · Newforma

CVE-2025-35051

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Project Center Server (NPCS) accepts serialized .NET data via the '/ProjectCenter.rem' endpoint on 9003/tcp, allowing a remote, unauthenticated attacker to execute arbitrary code with 'NT AUTHORITY\NetworkService' privileges. According to the recommended architecture, the vulnerable NPCS endpoint is only accessible on an internal network. To mitigate this vulnerability, restrict network access to NPCS.

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 confidence

Newforma Project Center Server contains a deserialization vulnerability (CWE-502) in its .NET remoting endpoint at '/ProjectCenter.rem' on TCP port 9003. The server accepts serialized .NET objects without authentication, allowing remote unauthenticated attackers to execute arbitrary code with NetworkService privileges.

MitigationRestrict network access to the NPCS service so it is only accessible from trusted internal network segments, not directly from the internet or untrusted networks.

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
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 checks

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

  1. Identify Newforma Project Center Server installation and version
    Locate the Newforma Project Center Server installation directory and check the installed version. Common locations include C:\Program Files\Newforma\Project Center Server or C:\Program Files (x86)\Newforma\Project Center Server. Look for version information in the application metadata, an 'about' dialog, or the executable's file properties.
    Affected if The installed version is exactly 2024.3
  2. Verify if TCP port 9003 is listening
    Run 'netstat -ano | findstr :9003' or use PowerShell 'Get-NetTCPConnection -LocalPort 9003' to check if the service is bound and listening on port 9003.
    Affected if Port 9003 is in a LISTENING state and bound to a Newforma process
  3. Confirm .NET remoting endpoint accessibility
    Attempt to access the endpoint by sending a test request to ProjectCenter.rem on port 9003 using a tool like netcat or PowerShell TCP client, or examine if the endpoint responds to serialized .NET object queries.
    Affected if The /ProjectCenter.rem endpoint responds to requests, indicating it is enabled and accepting connections
  4. Assess network exposure of the service
    Check the firewall rules and binding configuration to determine if port 9003 is accessible from external or untrusted network interfaces. Use 'netsh advfirewall firewall show rule name=all' or review the Windows Firewall inbound rules for the Newforma service.
    Affected if Port 9003 is allowed through the firewall for remote/untrusted network adapters, not restricted to localhost or trusted internal subnets only

You are affected if Newforma Project Center Server version 2024.3 is installed, the service is listening on TCP port 9003, the /ProjectCenter.rem endpoint is accessible, and port 9003 is exposed to untrusted network segments.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to the NPCS service so it is only accessible from trusted internal network segments, not directly from the internet or untrusted networks.

Fix this in Project Center Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,620
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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