# CVE-2024-32731: Missing Authorization check in SAP My Travel Requests

> An authenticated attacker can upload malicious attachments to business trip requests due to missing authorization checks, leading to privilege escalation.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-xqh8-8m3p-c72r

## What is CVE-2024-32731?

CVE-2024-32731 is a medium-severity missing authorization vulnerability in SAP_SE SAP My Travel Requests , published on 14 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

SAP My Travel Requests does not perform necessary authorization checks for an authenticated user, resulting in escalation of privileges. On successful exploitation, the attacker can upload a malicious attachment to a business trip request which will lead to a low impact on the confidentiality, integrity and availability of the application.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-32731?


## How do I fix CVE-2024-32731?

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

## Is CVE-2024-32731 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32731 and fix it if it is affected.

What it is: CVE-2024-32731 is a medium-severity missing authorization vulnerability in SAP_SE SAP My Travel Requests , published on 14 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-32731 in the wild and no public exploit code.

Affected product: SAP_SE SAP My Travel Requests . 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-2024-32731/ (Markdown: https://insights.sbomify.com/CVE-2024-32731/index.md)
```

## Sources

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

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