dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-4375

MEDIUM · 6.9 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 →
73/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
Cross-Site Request Forgery (CSRF) vulnerability in Sparx Systems Pro Cloud Server allows Cross-Site Request Forgery to perform Session Hijacking. Cross-Site Request Forgery is present at the whole application but it can be used to change the Pro Cloud Server Configuration password. This issue affects Pro Cloud Server: earlier than 6.0.165.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in Sparx Systems Pro Cloud Server allows authenticated users to be tricked into performing unintended actions, specifically changing the Pro Cloud Server Configuration password. This password change can lead to session hijacking as attackers can then access the system with the newly set credentials. The vulnerability affects all endpoints in the application and exists in versions earlier than 6.0.165.

MitigationUpgrade to Pro Cloud Server version 6.0.165 or later. Additionally, implement anti-CSRF tokens for all state-changing operations and configure SameSite cookie attributes as a defense-in-depth measure.

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
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:N/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. Identify installed Pro Cloud Server version
    Access the Pro Cloud Server administration interface or check the software installation directory for version information. Common locations include the About section in the admin panel or the server's main executable/dll properties.
    Affected if The installed version is earlier than 6.0.165 (for example, 6.0.160 or any version number less than 6.0.165)
  2. Verify access to Configuration password settings
    Log into the Pro Cloud Server admin interface and navigate to the Configuration or Settings section where the Pro Cloud Server Configuration password can be modified.
    Affected if The password change interface is accessible to authenticated users without additional verification steps
  3. Check for anti-CSRF token implementation
    Examine the web requests when changing the Configuration password. Inspect the HTML forms or API calls to determine if a unique anti-CSRF token is required and validated for each state-changing request.
    Affected if The password change request does not require a unique, session-bound anti-CSRF token

A user is affected if their Pro Cloud Server version is earlier than 6.0.165 AND the password change functionality lacks anti-CSRF token protection.

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

Upgrade to Pro Cloud Server version 6.0.165 or later. Additionally, implement anti-CSRF tokens for all state-changing operations and configure SameSite cookie attributes as a defense-in-depth measure.

Recommended fix High confidence

6.0.165 or later

  1. 1. Identify the current version of Sparx Systems Pro Cloud Server installed in your environment
  2. 2. Navigate to the official Sparx Systems download page at sparxsystems.com
  3. 3. Download Pro Cloud Server version 6.0.165 or later
  4. 4. Back up your current Pro Cloud Server configuration and database before upgrading
  5. 5. Install the new version following Sparx Systems' standard upgrade procedures
  6. 6. Verify the upgrade was successful by checking the installed version
  7. 7. Confirm the CSRF protection is now properly implemented

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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