# CVE-2025-42998: Security misconfiguration vulnerability in SAP Business One Integration Framework

> Attackers can bypass 403 Forbidden restrictions to access restricted pages in SAP Business One Integration Framework due to inadequate security settings.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2025
- **Updated:** 10 Jun 2025
- **Also known as:** GHSA-gw6j-cw44-6794

## What is CVE-2025-42998?

CVE-2025-42998 is a medium-severity missing authorization vulnerability in SAP_SE SAP Business One Integration Framework, published on 10 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The security settings in the SAP Business One Integration Framework are not adequately checked, allowing attackers to bypass the 403 Forbidden error and access restricted pages. This leads to low impact on confidentiality of the application, there is no impact on integrity and availability.

Weakness: CWE-346 (Origin Validation Error)

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


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

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

## Is CVE-2025-42998 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42998 is a medium-severity missing authorization vulnerability in SAP_SE SAP Business One Integration Framework, published on 10 Jun 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-42998 in the wild and no public exploit code.

Affected product: SAP_SE SAP Business One Integration Framework. 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-42998/ (Markdown: https://insights.sbomify.com/CVE-2025-42998/index.md)
```

## Sources

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

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