{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-45887 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-45887 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-45887 is a critical server-side request forgery vulnerability in n/a, published on 9 May 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-45887 and fix it if it is affected.\n\nWhat it is: CVE-2025-45887 is a critical server-side request forgery vulnerability in n/a, published on 9 May 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-45887 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-45887/ (Markdown: https://insights.sbomify.com/CVE-2025-45887/index.md)","id":"CVE-2025-45887","markdown":"https://insights.sbomify.com/CVE-2025-45887/index.md","name":"CVE-2025-45887","record":{"aliases":["GHSA-px42-xr3h-wjv8"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Yifang CMS","requires_auth":"none","summary":"An attacker can exploit an SSRF vulnerability in Yifang CMS to make the server send requests to arbitrary destinations, potentially accessing internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yifang","vendor":"wanglongcn"}],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Yifang CMS v2.0.2 is vulnerable to Server-Side Request Forgery (SSRF) in /api/file/getRemoteContent.","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":"Server-side request forgery in n/a","id":"CVE-2025-45887","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2025-45890"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2025-45885"},"products":["n/a"],"published":"2025-05-09","related":[{"cvss_score":6.9,"headline":"YiFang CMS Migrate.php exportInstallTable information disclosure","id":"CVE-2025-9398","kev_date_added":null,"published":"2025-08-24"},{"cvss_score":5.3,"headline":"YiFang CMS L_tool.php sql injection","id":"CVE-2025-9399","kev_date_added":null,"published":"2025-08-25"},{"cvss_score":5.3,"headline":"YiFang CMS P_file.php mergeMultipartUpload unrestricted upload","id":"CVE-2025-9400","kev_date_added":null,"published":"2025-08-25"},{"cvss_score":5.1,"headline":"YiFang CMS Backend File.php webUploader unrestricted upload","id":"CVE-2025-11136","kev_date_added":null,"published":"2025-09-29"},{"cvss_score":5.1,"headline":"Yifang CMS Admin Panel downloadFile path traversal","id":"CVE-2025-5381","kev_date_added":null,"published":"2025-05-31"},{"cvss_score":4.8,"headline":"Yifang CMS Article Management Module cross site scripting","id":"CVE-2025-5383","kev_date_added":null,"published":"2025-05-31"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-12","vendors":["n/a"]},"summary":"An attacker can exploit an SSRF vulnerability in Yifang CMS to make the server send requests to arbitrary destinations, potentially accessing internal resources.","url":"https://insights.sbomify.com/CVE-2025-45887/"}