{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60541 exists.","fix":"No fix has been published for CVE-2025-60541 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-60541 is a high-severity server-side request forgery vulnerability in n/a, published on 6 Nov 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-60541 and fix it if it is affected.\n\nWhat it is: CVE-2025-60541 is a high-severity server-side request forgery vulnerability in n/a, published on 6 Nov 2025. 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-2025-60541 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-2025-60541/ (Markdown: https://insights.sbomify.com/CVE-2025-60541/index.md)","id":"CVE-2025-60541","markdown":"https://insights.sbomify.com/CVE-2025-60541/index.md","name":"CVE-2025-60541","record":{"aliases":["GHSA-96fr-vhf8-gmqq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"prompt-optimizer","requires_auth":"none","summary":"Attackers can scan internal resources via crafted requests in the prompt-optimizer API proxy component.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"prompt_optimizer","vendor":"linshenkx"}],"cvss":{"score":7.3,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A Server-Side Request Forgery (SSRF) in the /api/proxy/ component of linshenkx prompt-optimizer v1.3.0 to v1.4.2 allows attackers to scan internal resources via a crafted request.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Server-side request forgery in n/a","id":"CVE-2025-60541","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"TypeORM vulnerable to SQL injection via crafted request to repository.save or repository.update","id":"CVE-2025-60542"},"packages":[],"prev":{"headline":"Server-side request forgery in n/a","id":"CVE-2025-60540"},"products":["n/a"],"published":"2025-11-06","related":[],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-07","vendors":["n/a"]},"summary":"Attackers can scan internal resources via crafted requests in the prompt-optimizer API proxy component.","url":"https://insights.sbomify.com/CVE-2025-60541/"}