{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-57212 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-57212 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-57212 is a high-severity missing authorization vulnerability in n/a, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-57212 and fix it if it is affected.\n\nWhat it is: CVE-2025-57212 is a high-severity missing authorization vulnerability in n/a, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-57212 in the wild and no public exploit code.\n\nAffected product: n/a. 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-57212/ (Markdown: https://insights.sbomify.com/CVE-2025-57212/index.md)","id":"CVE-2025-57212","markdown":"https://insights.sbomify.com/CVE-2025-57212/index.md","name":"CVE-2025-57212","record":{"aliases":["GHSA-x759-3r22-jq22"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"platform application","requires_auth":"none","summary":"Attackers can access sensitive information via crafted requests due to incorrect access control in the ApiOrderService component.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"platform","vendor":"fuyang_lipengjun"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"Incorrect access control in the component ApiOrderService.java of platform v1.0.0 allows attackers to access sensitive information via a crafted request.","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 in n/a","id":"CVE-2025-57212","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":"Missing authorization in n/a","id":"CVE-2025-57213"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2025-57210"},"products":["n/a"],"published":"2025-12-04","related":[{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2025-57210","kev_date_added":null,"published":"2025-12-04"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2025-57213","kev_date_added":null,"published":"2025-12-04"},{"cvss_score":5.3,"headline":"fuyang_lipengjun platform queryAll UserCouponController improper authorization","id":"CVE-2025-10819","kev_date_added":null,"published":"2025-09-22"},{"cvss_score":5.3,"headline":"fuyang_lipengjun platform queryAll TopicController improper authorization","id":"CVE-2025-10820","kev_date_added":null,"published":"2025-09-22"},{"cvss_score":5.3,"headline":"fuyang_lipengjun platform queryAll TopicCategoryController improper authorization","id":"CVE-2025-10821","kev_date_added":null,"published":"2025-09-22"},{"cvss_score":5.3,"headline":"fuyang_lipengjun platform queryAll SysSmsLogController improper authorization","id":"CVE-2025-10822","kev_date_added":null,"published":"2025-09-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-12-05","vendors":["n/a"]},"summary":"Attackers can access sensitive information via crafted requests due to incorrect access control in the ApiOrderService component.","url":"https://insights.sbomify.com/CVE-2025-57212/"}