{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-31333 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-31333 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-31333 is a medium-severity vulnerability in SAP_SE SAP S4CORE entity, published on 8 Apr 2025."},"fix_prompt":"Check this codebase for CVE-2025-31333 and fix it if it is affected.\n\nWhat it is: CVE-2025-31333 is a medium-severity vulnerability in SAP_SE SAP S4CORE entity, published on 8 Apr 2025. \nExploitation: There is no known exploitation of CVE-2025-31333 in the wild and no public exploit code.\n\nAffected product: SAP_SE SAP S4CORE entity. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-31333/ (Markdown: https://insights.sbomify.com/CVE-2025-31333/index.md)","id":"CVE-2025-31333","markdown":"https://insights.sbomify.com/CVE-2025-31333/index.md","name":"CVE-2025-31333","record":{"aliases":["GHSA-hw3g-3mvq-wr6f"],"analysis":null,"analysis_generated_by":null,"assigner":"sap","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-472","name":"External Control of Assumed-Immutable Web Parameter"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Odata meta-data tampering in SAP S4CORE entity","id":"CVE-2025-31333","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in WinRAR","id":"CVE-2025-31334"},"packages":[],"prev":{"headline":"Insecure File permissions vulnerability in SAP BusinessObjects Business Intelligence Platform","id":"CVE-2025-31332"},"products":["SAP S4CORE entity"],"published":"2025-04-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-08","vendors":["SAP_SE"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-31333/"}