CVE-2025-15622
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 · uneditedInsufficiently Protected Credentials vulnerability in Sparx Systems Pty Ltd. Sparx Enterprise Architect. Client reveals plaintext OAuth2 client secretDesktop client decodes the secret and uses the plaintext secret to exchange it into an access and id tokens as part of the OpenID authentication flow.
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 confidenceThe Sparx Enterprise Architect desktop client exposes OAuth2 client credentials in plaintext, where the client decodes and directly uses the plaintext secret to exchange for access and ID tokens during OpenID authentication, allowing credential exposure.
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
- Local
- Complexity
- Low
- Privileges
- None
- Authentication
- Y
- User interaction
- None
- Scope
- P
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:H/SI:L/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:P/AU:Y/R:X/V:C/RE:M/U:Red
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.
-
Confirm Sparx Enterprise Architect installationCheck for Enterprise Architect installation by looking in Program Files for 'Sparx Systems' folder, or search for EA.exe. Also check Add/Remove Programs for 'Enterprise Architect'.Affected if Sparx Enterprise Architect desktop client is installed on the system
-
Identify OpenID/OAuth2 authentication configurationLook for Enterprise Architect configuration files (e.g., .eap files, EA.config, or registry entries under HKEY_CURRENT_USER\Software\Sparx Systems) that contain OpenID, OAuth, or authentication-related settings.Affected if OpenID or OAuth2 authentication is configured for use with the client
-
Inspect credential storage locationsExamine Enterprise Architect configuration directories and files for plaintext OAuth client_id and client_secret values. Check common config locations: %APPDATA%\Sparx Systems\Enterprise Architect\, or any .config files associated with the installation.Affected if OAuth client credentials (client_id, client_secret) are found stored in plaintext configuration files or registry
-
Check for decoded secret usageMonitor network traffic during Enterprise Architect authentication using a proxy or packet capture. Observe if the client sends client_id and client_secret in the token request body. Look for the 'client_secret' parameter being transmitted.Affected if The client transmits OAuth client_secret in plaintext during token exchange requests
A user is affected if they use Sparx Enterprise Architect with OpenID/OAuth2 authentication and their client credentials are stored or transmitted in plaintext rather than using secure credential storage mechanisms.
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 secure credential storage mechanisms (e.g., OS credential manager, encrypted storage) and avoid plaintext secret handling in the client; consider moving to PKCE flow or confidential client pattern.
- Consultation6.0 h
- Implementation20.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15622 — 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-15622 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