CVE-2025-15621
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 in Sparx Systems Pty Ltd. Sparx Enterprise Architect. Client does not verify the receiver of OAuth2 credentials during OpenID authentication
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 confidenceThe Sparx Enterprise Architect client fails to verify the intended recipient of OAuth2 credentials during OpenID authentication, potentially allowing credential interception via a man-in-the-middle attack where an attacker positions themselves between the client and the legitimate authorization server.
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
- High
- Privileges
- Low
- Authentication
- Y
- User interaction
- P
- Scope
- P
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:H/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: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 checksWork through these to decide whether this CVE applies to you.
-
Check if Enterprise Architect OAuth2/OpenID authentication is enabledExamine EA client settings, configuration files, or registry for OAuth2/OpenID client configuration. Look for settings related to authentication type, OpenID provider, or OAuth2 authorization endpoints.Affected if OAuth2/OpenID authentication is configured and active in the Enterprise Architect client
-
Identify the configured OAuth2 token endpointLocate the OAuth2 authorization server configuration in EA client settings, config files, or registry. Record the token endpoint URL that the client is configured to use.Affected if A token endpoint URL is defined for OAuth2 authentication
-
Verify recipient/audience validation configurationReview OAuth2 client settings or related configuration for any audience (aud) or recipient validation parameters. Check if the client verifies that tokens are intended for its own identifier before accepting credentials.Affected if No audience/recipient validation is configured or the client accepts tokens without verifying intended recipient
-
Confirm man-in-the-middle exposureTest authentication flow in a controlled environment using a proxy to observe whether the client sends credentials to the configured endpoint without first validating server identity or token audience.Affected if Client transmits OAuth2 credentials without validating the authorization server's identity or token audience
A user is affected if the Enterprise Architect client uses OAuth2/OpenID authentication and the client does not validate that credentials are intended for its own identity before transmitting them to the authorization server.
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 proper recipient/audience validation in the OAuth2 client to verify the authorization server's identity before transmitting credentials, ensuring the token endpoint URL matches expected values.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15621 — 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-15621 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