CVE-2025-35055
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/UploadBlueimp.ashx' allows an authenticated attacker to upload an arbitrary file to any location writable by the NIX application. An attacker can upload and run a web shell or other content executable by the web server. An attacker can also delete directories. In Newforma before 2023.1, anonymous access is enabled by default (CVE-2025-35062), allowing an otherwise unauthenticated attacker to effectively authenticate as 'anonymous' and exploit this file upload vulnerability.
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 a file upload vulnerability in '/UserWeb/Common/UploadBlueimp.ashx' that allows authenticated attackers to upload arbitrary files to any location writable by the NIX application, including web-accessible directories where they can be executed as web shells. The vulnerability also permits directory deletion. When combined with CVE-2025-35062 (anonymous access enabled by default before v2023.1), unauthenticated attackers can effectively authenticate as 'anonymous' and exploit this vulnerability.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check Newforma Project Center versionLocate the installed Newforma Project Center version by checking the application itself (typically via Help > About in the desktop client) or by inspecting the Windows Programs and Features list, or the NIX web application headers/version file if accessible.Affected if The installed version is earlier than 2023.1 (e.g., 2022.x, 2021.x, etc.)
-
Verify UploadBlueimp.ashx endpoint existsAttempt to access the file /UserWeb/Common/UploadBlueimp.ashx on the NIX web server (e.g., https://yourserver/UserWeb/Common/UploadBlueimp.ashx) using a web browser or curl command. A 404 response indicates the file may not exist, while any response (including errors) indicates the endpoint is present.Affected if The endpoint returns any HTTP response other than 404, indicating it exists on the server.
-
Check if anonymous authentication is enabledReview the NIX web configuration (web.config file in the UserWeb directory) for authentication settings, specifically look for <authentication mode="Anonymous"> or equivalent settings that allow unauthenticated access to the UploadBlueimp.ashx handler.Affected if Anonymous authentication is enabled or the application accepts requests without valid credentials, allowing unauthenticated access to upload functionality.
-
Inspect upload directory permissionsReview the file system permissions on the NIX upload directories (typically under the UserWeb folder) and check if any directories are writable by the application pool identity. Specifically examine whether web-accessible directories (wwwroot, inetpub, or similar) are writable by the NIX service account.Affected if Upload directories or web root directories are writable by the NIX application service account, allowing uploaded files to be placed in web-accessible locations.
-
Check for suspicious uploaded filesSearch the UserWeb directory tree and any known upload folders for file types that should not be present, such as .asp, .aspx, .php, .exe, .cmd, or other script/executable extensions. Also note any unexpected directories that may have been created.Affected if Unexpected files with executable extensions (especially .aspx web shells) or unexpected directories are found in web-accessible paths.
The environment is affected if Newforma Project Center version is below 2023.1 AND the UploadBlueimp.ashx endpoint exists AND (anonymous access is enabled OR valid credentials are available), with writeable upload directories allowing placement of files in web-accessible locations.
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.
From vendor data2023.1
Upgrade to Newforma 2023.1 or later to disable anonymous access by default, and implement strict allowlist-based file validation, restrict upload directory permissions to prevent execution, and remove write access from web-root directories.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-35055 — 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-35055 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