{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-42899 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-42899 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-42899 is a medium-severity missing authorization vulnerability in SAP_SE SAP S4CORE (Manage Journal Entries), published on 11 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-42899 and fix it if it is affected.\n\nWhat it is: CVE-2025-42899 is a medium-severity missing authorization vulnerability in SAP_SE SAP S4CORE (Manage Journal Entries), published on 11 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-42899 in the wild and no public exploit code.\n\nAffected product: SAP_SE SAP S4CORE (Manage Journal Entries). 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-42899/ (Markdown: https://insights.sbomify.com/CVE-2025-42899/index.md)","id":"CVE-2025-42899","markdown":"https://insights.sbomify.com/CVE-2025-42899/index.md","name":"CVE-2025-42899","record":{"aliases":["GHSA-pg79-24mp-wrx5"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SAP S4CORE","requires_auth":"low_privilege","summary":"An authenticated user can escalate privileges and read confidential data in SAP S4CORE due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","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:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"SAP S4CORE (Manage journal entries) does not perform necessary authorization checks for an authenticated user resulting in escalation of privileges. This has low impact on confidentiality of the application with no impact on integrity and availability of the application.","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":"Missing Authorization check in SAP S4CORE (Manage Journal Entries)","id":"CVE-2025-42899","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Code Injection vulnerability in SAP Application Server for ABAP (BAPI Browser)","id":"CVE-2025-42901"},"packages":[],"prev":{"headline":"Information Disclosure vulnerability in SAP Business One (SLD)","id":"CVE-2025-42897"},"products":["SAP S4CORE (Manage Journal Entries)"],"published":"2025-11-11","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-11-12","vendors":["SAP_SE"]},"summary":"An authenticated user can escalate privileges and read confidential data in SAP S4CORE due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2025-42899/"}