{"answers":{"affected":"1 open source package ship an affected version, including lollms. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0560 exists.","fix":"Upgrade lollms to 2.1.1 or later.","what":"CVE-2026-0560 is a high-severity server-side request forgery vulnerability in parisneo/lollms, published on 29 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-0560 and fix it if it is affected.\n\nWhat it is: CVE-2026-0560 is a high-severity server-side request forgery vulnerability in parisneo/lollms, published on 29 Mar 2026. 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-2026-0560 exists.\n\nAffected packages and fixed versions:\n- lollms (PyPI): affected all versions; fixed in 2.1.1\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-2026-0560/ (Markdown: https://insights.sbomify.com/CVE-2026-0560/index.md)","id":"CVE-2026-0560","markdown":"https://insights.sbomify.com/CVE-2026-0560/index.md","name":"CVE-2026-0560","record":{"aliases":["GHSA-rqmp-494m-8qgf","PYSEC-2026-2199"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"lollms web application","requires_auth":"none","summary":"Attackers can exploit an SSRF vulnerability in the file export endpoint to access internal services and potentially execute remote code.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"lollms","vendor":"lollms"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A Server-Side Request Forgery (SSRF) vulnerability exists in parisneo/lollms versions prior to 2.2.0, specifically in the `/api/files/export-content` endpoint. The `_download_image_to_temp()` function in `backend/routers/files.py` fails to validate user-controlled URLs, allowing attackers to make arbitrary HTTP requests to internal services and cloud metadata endpoints. This vulnerability can lead to internal network access, cloud metadata access, information disclosure, port scanning, and potentially remote code execution.","ecosystems":["PyPI"],"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/2026/CVE-2026-0560.yaml","stars":null,"title":"LolLMS \u003c 2.2.0 - Server-Side Request Forgery"}],"tier":"weaponised"},"has_fix":true,"headline":"Server-Side Request Forgery (SSRF) in parisneo/lollms","id":"CVE-2026-0560","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":1,"n_references":2,"next":{"headline":"Shield Security \u003c= 21.0.8 - Unauthenticated Reflected Cross-Site Scripting via 'message' Parameter","id":"CVE-2026-0561"},"packages":[{"ecosystem":"PyPI","fixed":["2.1.1"],"introduced":["0"],"last_affected":[],"package":"lollms","purl":"pkg:pypi/lollms","source":"PYSEC-2026-2199"}],"prev":{"headline":"Cross-site scripting in MasterStudy LMS WordPress Plugin – for Online Courses and Education","id":"CVE-2026-0559"},"products":["parisneo/lollms"],"published":"2026-03-29","related":[{"cvss_score":9.8,"headline":"Improper Access Control via Weak JWT Token in parisneo/lollms","id":"CVE-2026-1114","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":9.8,"headline":"Path Traversal in parisneo/lollms","id":"CVE-2024-3429","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":9.6,"headline":"Stored XSS in parisneo/lollms","id":"CVE-2026-1115","kev_date_added":null,"published":"2026-04-10"},{"cvss_score":8.7,"headline":"Stored XSS in Direct Messages via Prompt Sharing in parisneo/lollms","id":"CVE-2026-12228","kev_date_added":null,"published":"2026-07-18"},{"cvss_score":8.3,"headline":"Insecure Direct Object Reference (IDOR) in parisneo/lollms","id":"CVE-2026-0562","kev_date_added":null,"published":"2026-03-29"},{"cvss_score":8.2,"headline":"Cross-site Scripting (XSS) in parisneo/lollms","id":"CVE-2026-1116","kev_date_added":null,"published":"2026-04-12"},{"cvss_score":7.6,"headline":"CSRF Vulnerability in parisneo/lollms XTTS Server","id":"CVE-2024-4499","kev_date_added":null,"published":"2024-06-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-03-30","vendors":["parisneo"]},"summary":"Attackers can exploit an SSRF vulnerability in the file export endpoint to access internal services and potentially execute remote code.","url":"https://insights.sbomify.com/CVE-2026-0560/"}