dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-7719

MEDIUM · 5.3 CVSS v4.0 Published 2025-11-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in GE Vernova Smallworld on Windows, Linux allows File Manipulation.This issue affects Smallworld: 5.3.5. and previous versions.

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

A path traversal vulnerability in GE Vernova Smallworld allows attackers to manipulate file paths using '..' sequences to access files outside restricted directories. This affects both Windows and Linux platforms, enabling unauthorized file manipulation operations.

MitigationApply vendor-supplied patch for Smallworld 5.3.5 or upgrade to fixed version; in the interim, implement strict input validation on file path parameters and restrict file system permissions to limit the impact of exploitation.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/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 checks

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

  1. Confirm GE Vernova Smallworld installation
    Locate Smallworld installation directories (typically in /opt/smallworld or C:\Program Files\GE Vernova\Smallworld on Linux/Windows). Check for smallworld_core, smallworld_gis, or similar product directories.
    Affected if Smallworld software is present on the system
  2. Identify installed Smallworld version
    Check version files or executables in the installation directory. Common locations: version.txt, about dialog, or run 'smallworld -version' if CLI available. Compare against the 5.3.5 affected range.
    Affected if Version is 5.3.5 or falls within an unpatched range prior to the vendor fix
  3. Determine if file path handling modules are in use
    Review Smallworld configuration files (e.g., sw_config, magik files in config/ or core/ directories) for modules that handle file paths, uploads, or file system operations. Look for functions like file_open, path manipulation, or document management features.
    Affected if File path or document handling modules are enabled and accessible to users
  4. Check for exposed file operation interfaces
    Inspect Smallworld service configurations, web interfaces, or API endpoints that accept file path parameters. Review magik scripts for user-facing file operations that could accept '..' sequences.
    Affected if User-accessible interfaces accept file path input without documented validation layers
  5. Verify file system permission boundaries
    Review file system ACLs and access controls on Smallworld data directories. Check if the application process runs with elevated privileges that could allow traversal beyond intended directories.
    Affected if Application has broad file system access or runs with privileges exceeding necessary scope

A system is affected if it runs GE Vernova Smallworld 5.3.5 or an unpatched version with accessible file path handling features that accept user input without traversal validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patch for Smallworld 5.3.5 or upgrade to fixed version; in the interim, implement strict input validation on file path parameters and restrict file system permissions to limit the impact of exploitation.

Recommended fix Moderate confidence

Smallworld version higher than 5.3.5 (contact GE Vernova for exact fixed version)

  1. Contact GE Vernova support to obtain the latest Smallworld version that includes the path traversal fix
  2. Request confirmation of the specific version number containing the security patch for CVE-2025-7719
  3. Plan upgrade in a non-production environment first
  4. Backup all Smallworld configuration and data files
  5. Execute upgrade following GE Vernova's official upgrade documentation
  6. Verify the fix by testing file access paths to ensure proper directory restriction is enforced
Caveat Review GE Vernova upgrade guide for any configuration or compatibility changes between 5.3.5 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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