Improper Input ValidationWeakness · CWE-20

CVE-2025-4377

HIGH · 8.3 CVSS v4.0 Published 2025-05-09

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

89/100

Remediation priority · High

Remotely reachable Zero-click

Official description

NVD · unedited

Improper Limitation of a Pathname caused a Path Traversal vulnerability in Sparx Systems Pro Cloud Server. This vulnerability is present in logview.php and it allows reading arbitrary files on the filesystem. Logview is accessible on Pro Cloud Server Configuration interface. This issue affects Pro Cloud Server: earlier than 6.0.165.

Technical summary

dbcve analysis · high confidence

A path traversal vulnerability in logview.php in Sparx Systems Pro Cloud Server allows attackers to read arbitrary files on the filesystem by manipulating path inputs. The logview component in the Pro Cloud Server Configuration interface does not properly validate or sanitize user-supplied path parameters, enabling traversal outside the intended directory.

MitigationUpgrade Pro Cloud Server to version 6.0.165 or later to obtain the patch. Until then, restrict network access to the Pro Cloud Server Configuration interface to reduce exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

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:L/SC:H/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?

dbcve checks

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

Confirm Pro Cloud Server installation

Locate the Pro Cloud Server installation directory, typically in Program Files/Sparx Systems/Pro Cloud Server, or check Windows Services for 'Pro Cloud Server' service

Affected if Pro Cloud Server is installed and running
Identify installed version

Check the version of Pro Cloud Server - look in the installation directory for version.txt, or right-click the Pro Cloud Server service in Windows Services and view the executable path which typically includes version info, or access the Pro Cloud Server Configuration interface and check the about/version section

Affected if Version is lower than 6.0.165 (vulnerable versions)
Verify Configuration interface is accessible

Attempt to access the Pro Cloud Server Configuration interface web portal (typically on port 18080 or 18081) and navigate to the logview component

Affected if The Configuration interface is exposed and logview.php is reachable
Check logview.php accessibility

Access the logview.php endpoint directly via the Configuration interface URL (e.g., http://server:port/logview.php or within the /configuration/ path)

Affected if logview.php is accessible without authentication or with valid credentials, indicating the path traversal attack surface exists

A user is affected if Pro Cloud Server version is below 6.0.165 AND the Configuration interface with logview.php is accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade Pro Cloud Server to version 6.0.165 or later to obtain the patch. Until then, restrict network access to the Pro Cloud Server Configuration interface to reduce exposure.

Recommended fix High confidence

Pro Cloud Server 6.0.165 or later

Download Pro Cloud Server version 6.0.165 or later from the official Sparx Systems download portal at sparxsystems.com
Backup your current Pro Cloud Server configuration and database
Install or upgrade to Pro Cloud Server 6.0.165 or newer
Verify the installation was successful
Access the Pro Cloud Server Configuration interface and confirm logview.php is accessible and functioning properly
Test that the path traversal vulnerability is remediated by confirming logview.php now properly validates and restricts path inputs

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

Have this fixed Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing12.0 h
Review / QA4.0 h

28.0 hours of engineering $4,760

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

sparxsystems.com
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-4377 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-4377?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 8.3 High

Exploit likelihood EPSS, next 30 days 0.7%

Remediation

A high-priority fix

Have this fixed 28 hrs · Moderate

Typical engagement from $4,760

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-4377 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References