dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-4376

MEDIUM · 5.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 →
60/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Input Validation vulnerability in Sparx Systems Pro Cloud Server's WebEA model search field allows Cross-Site Scripting (XSS). 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 · moderate confidence

Sparx Systems Pro Cloud Server's WebEA component contains an improper input validation vulnerability in the model search field that allows attackers to inject malicious JavaScript code (XSS). Users who view search results containing the injected payload will have the script executed in their browser context.

MitigationUpgrade Pro Cloud Server to version 6.0.165 or later to obtain the patched version. As a temporary mitigation, restrict access to WebEA until the upgrade can be applied.

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

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

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

  1. Identify Pro Cloud Server installation location
    Locate the Pro Cloud Server installation directory, typically in C:\Program Files\Sparx Systems\Pro Cloud Server on Windows or /opt/sparxsystems/pro_cloud_server on Linux
    Affected if Pro Cloud Server is installed and running
  2. Determine Pro Cloud Server version
    Check the server version by inspecting the About section in the Pro Cloud Server administration interface, or check the version info in the installation directory (often in a version.txt, about dialog, or in the binary properties)
    Affected if The installed version is lower than 6.0.165 (vulnerable versions are prior to the 6.0.165 patch release)
  3. Confirm WebEA component is enabled
    Access the Pro Cloud Server configuration or administration panel and verify that WebEA (Web Enterprise Architecture) module is enabled and accessible
    Affected if WebEA is enabled and publicly or internally accessible
  4. Verify model search feature is accessible
    Log into WebEA and navigate to the model search functionality to confirm it is available as an entry point for the XSS vulnerability
    Affected if The model search field is accessible to users (authenticated or anonymous)

You are affected if Pro Cloud Server version is below 6.0.165 AND WebEA with the model search feature is enabled and accessible to users.

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 Pro Cloud Server to version 6.0.165 or later to obtain the patched version. As a temporary mitigation, restrict access to WebEA until the upgrade can be applied.

Recommended fix Moderate confidence

Pro Cloud Server 6.0.165 or later

  1. Obtain Pro Cloud Server version 6.0.165 or later from the official Sparx Systems download repository
  2. Follow the standard Pro Cloud Server upgrade procedure as documented in the Sparx Systems installation guide
  3. Verify the upgrade was successful by checking the Pro Cloud Server version
  4. Confirm the WebEA model search field no longer permits XSS by testing with benign input

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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