# CVE-2025-30016: Authentication Bypass Vulnerability in SAP Financial Consolidation

> Unauthenticated attackers can bypass authentication to gain admin access, compromising confidentiality, integrity, and availability.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-4wrv-c229-vc5p

## What is CVE-2025-30016?

CVE-2025-30016 is a critical authentication bypass vulnerability in SAP_SE SAP Financial Consolidation, published on 8 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SAP Financial Consolidation allows an unauthenticated attacker to gain unauthorized access to the Admin account. The vulnerability arises due to improper authentication mechanisms, due to which there is high impact on the Confidentiality, Integrity & Availability of the application.

Weakness: CWE-921 (Storage of Sensitive Data in a Mechanism without Access Control)

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


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

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

## Is CVE-2025-30016 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30016 is a critical authentication bypass vulnerability in SAP_SE SAP Financial Consolidation, published on 8 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30016 in the wild and no public exploit code.

Affected product: SAP_SE SAP Financial Consolidation. 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-30016/ (Markdown: https://insights.sbomify.com/CVE-2025-30016/index.md)
```

## Sources

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

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