Authenticated entity tampering via writable OData metadata
Published Apr 22, 2025 · Updated Apr 23, 2025
Data tampering in SAP Field Logistics S4CORE 107 and 108 allows remote authenticated users to modify Manage Logistics entity fields. The Manage Logistics OData metadata marks certain entity properties as externally writable instead of immutable, accepting changes to fields that should be read-only. Low-privileged network access is required; the resulting changes affect application-data integrity without disclosed confidentiality or availability impact.
Summary
What happened
Data tampering in SAP Field Logistics S4CORE 107 and 108 allows remote authenticated users to modify Manage Logistics entity fields. The Manage Logistics OData metadata marks certain entity properties as externally writable instead of immutable, accepting changes to fields that should be read-only. Low-privileged network access is required; the resulting changes affect application-data integrity without disclosed confidentiality or availability impact.
The record
- CVE
- CVE-2025-31327
- Published
- Apr 22, 2025
- Updated
- Apr 23, 2025
- Vendor
- SAP SE
- Product
- SAP Field Logistics
- Classifications
- CWE-472, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 22, 2025CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=108
- Affected versionversion=S4CORE 107
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo