# CVE-2025-15621: Sparx Enterprise Architect Client does not verify the receiver of OAuth2 credentials during OpenID authentication

> Attackers can intercept OAuth2 credentials during OpenID authentication due to missing receiver verification, potentially leading to account takeover.

- **Severity:** Medium 5.7 (`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/S:P/AU:Y/V:C/RE:M`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Apr 2026
- **Updated:** 16 Apr 2026
- **Also known as:** GHSA-g8rx-2jmm-3847

## What is CVE-2025-15621?

CVE-2025-15621 is a medium-severity vulnerability in Sparx Enterprise Architect, published on 16 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Insufficiently Protected Credentials in Sparx Systems Pty Ltd. Sparx Enterprise Architect. Client does not verify the receiver of OAuth2 credentials during OpenID authentication

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2025-15621?

It affects 1 product.


Products: Sparxsystems Enterprise Architect.

## How do I fix CVE-2025-15621?

No fix has been published for CVE-2025-15621 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-15621 being exploited?

There is no known exploitation of CVE-2025-15621 in the wild and no public exploit code.

## Other vulnerabilities in Sparx Enterprise Architect

- [CVE-2022-47072](https://insights.sbomify.com/CVE-2022-47072/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15621 and fix it if it is affected.

What it is: CVE-2025-15621 is a medium-severity vulnerability in Sparx Enterprise Architect, published on 16 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-15621 in the wild and no public exploit code.

Affected product: Sparx Enterprise Architect. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-15621/ (Markdown: https://insights.sbomify.com/CVE-2025-15621/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15621
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15621
- OSV: https://osv.dev/vulnerability/CVE-2025-15621

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-15621/
Summaries are generated and may contain mistakes; the official description above is the record.