{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36675 exists.","fix":"No fix has been published for CVE-2024-36675 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-36675 is a critical server-side request forgery vulnerability in n/a, published on 4 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-36675 and fix it if it is affected.\n\nWhat it is: CVE-2024-36675 is a critical server-side request forgery vulnerability in n/a, published on 4 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36675 exists.\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-2024-36675/ (Markdown: https://insights.sbomify.com/CVE-2024-36675/index.md)","id":"CVE-2024-36675","markdown":"https://insights.sbomify.com/CVE-2024-36675/index.md","name":"CVE-2024-36675","record":{"aliases":["GHSA-6fjg-5w3q-x6m9"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"LyLme_spage","requires_auth":"none","summary":"An attacker can exploit a Server-Side Request Forgery vulnerability in LyLme_spage to make arbitrary requests from the server.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lylme_spage","vendor":"lylme"}],"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":"LyLme_spage v1.9.5 is vulnerable to Server-Side Request Forgery (SSRF) via the get_head function.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2024/CVE-2024-36675.yaml","stars":null,"title":"LyLme spage v1.9.5 - Server-Side Request Forgery"}],"tier":"weaponised"},"has_fix":false,"headline":"Server-side request forgery in n/a","id":"CVE-2024-36675","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"BookStack Incorrect Access Control vulnerability","id":"CVE-2024-36676"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-36674"},"products":["n/a"],"published":"2024-06-04","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2024-48176","kev_date_added":null,"published":"2024-11-05"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-48356","kev_date_added":null,"published":"2024-10-28"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-48357","kev_date_added":null,"published":"2024-10-28"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-34982","kev_date_added":null,"published":"2024-05-17"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-45951","kev_date_added":null,"published":"2023-10-17"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-45952","kev_date_added":null,"published":"2023-10-17"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["n/a"]},"summary":"An attacker can exploit a Server-Side Request Forgery vulnerability in LyLme_spage to make arbitrary requests from the server.","url":"https://insights.sbomify.com/CVE-2024-36675/"}