{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-36560 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-36560 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-36560 is a critical server-side request forgery vulnerability in appleple inc. a-blog cms, published on 19 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-36560 and fix it if it is affected.\n\nWhat it is: CVE-2025-36560 is a critical server-side request forgery vulnerability in appleple inc. a-blog cms, published on 19 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-36560 in the wild and no public exploit code.\n\nAffected product: appleple inc. a-blog cms. 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-36560/ (Markdown: https://insights.sbomify.com/CVE-2025-36560/index.md)","id":"CVE-2025-36560","markdown":"https://insights.sbomify.com/CVE-2025-36560/index.md","name":"CVE-2025-36560","record":{"aliases":["GHSA-9fjv-px63-6jvj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"a-blog cms","requires_auth":"none","summary":"Remote unauthenticated attackers can exploit a Server-Side Request Forgery flaw in a-blog cms to access sensitive information.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[{"product":"a-blog_cms","vendor":"appleple"}],"cvss":{"score":9.2,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Server-side request forgery vulnerability exists in a-blog cms multiple versions. If this vulnerability is exploited, a remote unauthenticated attacker may gain access to sensitive information by sending a specially 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":"Server-side request forgery in a-blog cms","id":"CVE-2025-36560","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in PowerCMS","id":"CVE-2025-36563"},"packages":[],"prev":{"headline":"KUNBUS Revolution Pi Improper Neutralization of Server-Side Includes (SSI) Within a Web Page","id":"CVE-2025-36558"},"products":["a-blog cms"],"published":"2025-05-19","related":[{"cvss_score":9.8,"headline":"Auth bypass in a-blog cms","id":"CVE-2022-21142","kev_date_added":null,"published":"2022-02-24"},{"cvss_score":8.8,"headline":"File upload in a-blog cms","id":"CVE-2024-23180","kev_date_added":null,"published":"2024-01-23"},{"cvss_score":8.8,"headline":"Cross-site scripting in a-blog cms","id":"CVE-2024-23348","kev_date_added":null,"published":"2024-01-23"},{"cvss_score":8.1,"headline":"Path traversal in a-blog cms","id":"CVE-2024-23182","kev_date_added":null,"published":"2024-01-23"},{"cvss_score":7.5,"headline":"Deserialization in a-blog cms (Ver. 2.8.x series)","id":"CVE-2025-31103","kev_date_added":null,"published":"2025-03-31"},{"cvss_score":6.6,"headline":"Code injection in a-blog cms Ver.3.0.x series","id":"CVE-2024-31396","kev_date_added":null,"published":"2024-05-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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-19","vendors":["appleple inc."]},"summary":"Remote unauthenticated attackers can exploit a Server-Side Request Forgery flaw in a-blog cms to access sensitive information.","url":"https://insights.sbomify.com/CVE-2025-36560/"}