CVE-2025-31333 Odata meta-data tampering in SAP S4CORE entity
Medium 4.3
Published
Updated
Check this codebase for CVE-2025-31333 and fix it if it is affected.
What it is: CVE-2025-31333 is a medium-severity vulnerability in SAP_SE SAP S4CORE entity, published on 8 Apr 2025.
Exploitation: There is no known exploitation of CVE-2025-31333 in the wild and no public exploit code.
Affected product: SAP_SE SAP S4CORE entity. 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-31333/ (Markdown: https://insights.sbomify.com/CVE-2025-31333/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2025-31333?
CVE-2025-31333 is a medium-severity vulnerability in SAP_SE SAP S4CORE entity, published on 8 Apr 2025.
Official 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.
Weakness: CWE-472
Which versions are affected by CVE-2025-31333?
How do I fix CVE-2025-31333?
No fix has been published for CVE-2025-31333 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-31333 being exploited?
There is no known exploitation of CVE-2025-31333 in the wild and no public exploit code.
Sources
Also known as GHSA-hw3g-3mvq-wr6f.