CVE-2025-0659
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 · uneditedA path traversal vulnerability exists in the Rockwell Automation DataEdge Platform DataMosaix Private Cloud. By specifying the character sequence in the body of the vulnerable endpoint, it is possible to overwrite files outside of the intended directory. A threat actor with admin privileges could leverage this vulnerability to overwrite reports including user projects.
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 confidenceA path traversal vulnerability in the Rockwell Automation DataEdge Platform DataMosaix Private Cloud allows an authenticated admin user to manipulate file paths using '../' sequences in endpoint requests, enabling overwrite of files outside the intended directory. This can affect reports and user projects stored on the system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 DataEdge Platform DataMosaix installationLocate the DataEdge Platform installation and determine the installed version by checking the application binaries, configuration files, or the product's built-in version information interface. Compare your version against the affected version range.Affected if The installed version falls within the vulnerable version range and the DataMosaix Private Cloud component is present.
-
Verify admin authentication is enabledCheck whether admin user authentication is configured and functional on the DataMosaix Private Cloud interface. Review user role configurations to confirm admin-level accounts exist.Affected if Admin authentication is enabled and admin users can access the platform, as this CVE requires an authenticated admin user to exploit the path traversal.
-
Identify file management endpointsExamine the web application's available endpoints, particularly those handling file operations such as report generation, project file storage, or file upload/download functionality.Affected if Endpoints that accept file path parameters are accessible to authenticated admin users.
-
Test for path traversal vulnerabilityUsing an authenticated admin session, attempt to access or manipulate file paths using '../' sequences in relevant endpoint requests to see if the application allows escaping the intended directory.Affected if The application accepts '../' sequences in file path parameters and allows file operations outside the intended directory boundary.
Your environment is affected if the DataEdge DataMosaix Private Cloud is running a vulnerable version, admin authentication is enabled, and file management endpoints accept path parameters that are not properly sanitized.
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 dataImplement strict input validation and path sanitization to ensure file paths resolve within the intended directory boundaries, preventing traversal outside allowed paths.
- Consultation4.0 h
- Implementation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0659 — 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-0659 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