{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-52082 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-52082 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-52082 is a high-severity SQL injection vulnerability in LycheeOrg Lychee, published on 28 Dec 2023. 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-2023-52082 and fix it if it is affected.\n\nWhat it is: CVE-2023-52082 is a high-severity SQL injection vulnerability in LycheeOrg Lychee, published on 28 Dec 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-52082 in the wild and no public exploit code.\n\nAffected product: LycheeOrg Lychee. 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-2023-52082/ (Markdown: https://insights.sbomify.com/CVE-2023-52082/index.md)","id":"CVE-2023-52082","markdown":"https://insights.sbomify.com/CVE-2023-52082/index.md","name":"CVE-2023-52082","record":{"aliases":["GHSA-rjwv-5j3m-p5x4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Lychee photo management","requires_auth":"none","summary":"Attackers can execute arbitrary SQL commands in Lychee if SQL logging is enabled, allowing data access or modification.","user_interaction":"required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"lychee","vendor":"lycheeorg"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Lychee is a free photo-management tool.  Prior to 5.0.2, Lychee is vulnerable to an SQL injection on any binding when using mysql/mariadb. This injection is only active for users with the `.env` settings set to DB_LOG_SQL=true and DB_LOG_SQL_EXPLAIN=true. The defaults settings of Lychee are safe.  The patch is provided on version 5.0.2.  To work around this issue, disable SQL EXPLAIN logging.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Lychee is vulnerable to an SQL Injection in explain DB queries.","id":"CVE-2023-52082","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Stored XSS through privileged upload of Media Manager file followed by renaming","id":"CVE-2023-52083"},"packages":[],"prev":{"headline":"ewen-lbh/ffcss late-Unicode normalization vulnerability","id":"CVE-2023-52081"},"products":["Lychee"],"published":"2023-12-28","related":[{"cvss_score":8.3,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-25808","kev_date_added":null,"published":"2024-03-22"},{"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-11-27","vendors":["LycheeOrg"]},"summary":"Attackers can execute arbitrary SQL commands in Lychee if SQL logging is enabled, allowing data access or modification.","url":"https://insights.sbomify.com/CVE-2023-52082/"}