{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25808 exists.","fix":"No fix has been published for CVE-2024-25808 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-25808 is a high-severity vulnerability in n/a, published on 22 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-25808 and fix it if it is affected.\n\nWhat it is: CVE-2024-25808 is a high-severity vulnerability in n/a, published on 22 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25808 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-25808/ (Markdown: https://insights.sbomify.com/CVE-2024-25808/index.md)","id":"CVE-2024-25808","markdown":"https://insights.sbomify.com/CVE-2024-25808/index.md","name":"CVE-2024-25808","record":{"aliases":["GHSA-386g-6xm2-mvq6"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Lychee photo manager","requires_auth":"none","summary":"A CSRF vulnerability in Lychee allows remote attackers to execute arbitrary code via the create new album function.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lychee","vendor":"lycheeorg"}],"cvss":{"score":8.3,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-site Request Forgery (CSRF) vulnerability in Lychee version 3.1.6, allows remote attackers to execute arbitrary code via the create new album function.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-25808","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2024-25811"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-25807"},"products":["n/a"],"published":"2024-03-22","related":[{"cvss_score":8.8,"headline":"Lychee is vulnerable to an SQL Injection in explain DB queries.","id":"CVE-2023-52082","kev_date_added":null,"published":"2023-12-28"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-25807","kev_date_added":null,"published":"2024-03-22"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2021-43675","kev_date_added":null,"published":"2021-12-15"},{"cvss_score":5.3,"headline":"Lychee has SSRF bypass via incomplete IP validation in Photo::fromUrl — loopback and link-local IPs not blocked","id":"CVE-2026-33537","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":4.8,"headline":"Lychee Vulnerable to Stored XSS via Photo Description in RSS/Atom/JSON Feed (No Sanitization on Public Endpoint)","id":"CVE-2026-33738","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":2.3,"headline":"Missing authorization in Lychee","id":"CVE-2026-39957","kev_date_added":null,"published":"2026-04-09"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-06","vendors":["n/a"]},"summary":"A CSRF vulnerability in Lychee allows remote attackers to execute arbitrary code via the create new album function.","url":"https://insights.sbomify.com/CVE-2024-25808/"}