Project CenterApplication · Newforma

CVE-2025-35060

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-09
Fix available
A fix is available. Upgrade to 2024.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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) provides a 'Send a File Transfer' feature that allows a remote, authenticated attacker to upload SVG files that contain JavaScript or other content that may be executed or rendered by a web browser using a mobile user agent.

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) contains a stored cross-site scripting (XSS) vulnerability in its 'Send a File Transfer' feature. Authenticated remote attackers can upload SVG files containing embedded JavaScript that executes when viewed in mobile web browsers, allowing theft of session tokens or other client-side attacks.

MitigationImplement server-side validation to strip or block JavaScript content from SVG files during upload, or disable SVG file uploads entirely. Apply strict Content-Security-Policy headers to mitigate script execution.

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

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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
    Locate the Newforma Project Center application on the system and determine its installation directory. Check for executable files, services, or installed programs named 'Newforma Project Center' or similar.
    Affected if Newforma Project Center is installed on the system
  2. Determine installed version
    Right-click on the Newforma Project Center executable or access the application's About/Help section to view the version number. Alternatively, check the Windows Programs and Features list, the application manifest, or any version file in the installation directory.
    Affected if The installed version is lower than 2024.1 (e.g., 2023.x, earlier versions)
  3. Verify Send a File Transfer feature exists
    Log into the Newforma Project Center application as an authenticated user. Navigate through the interface to locate the 'Send a File Transfer' feature, typically found in the file sharing or communication modules.
    Affected if The 'Send a File Transfer' feature is present and accessible to authenticated users
  4. Check if SVG uploads are permitted
    Within the Send a File Transfer feature, attempt to attach or upload an SVG file. Observe whether the application accepts SVG file extensions or check the application's upload configuration/settings for allowed file types.
    Affected if SVG file uploads are accepted by the application without server-side validation blocking them

The environment is affected if Newforma Project Center is installed with a version lower than 2024.1 and the Send a File Transfer feature allows authenticated users to upload SVG files.

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 2024.1 or later
Fixed in 2024.1
Interim mitigation

Implement server-side validation to strip or block JavaScript content from SVG files during upload, or disable SVG file uploads entirely. Apply strict Content-Security-Policy headers to mitigate script execution.

Recommended fix High confidence

2024.1 or later

  1. Upgrade Project Center to version 2024.1 or later to remediate the SVG XSS vulnerability
  2. After upgrading, verify that SVG file upload functionality still works correctly for legitimate use cases
  3. Test with a mobile user agent to confirm that SVG files are now properly sanitized and do not execute embedded JavaScript

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-35060 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