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.
CVE-2023-52082
“—” beside the score: it is equal to NVD's CVSS score.
This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8CRITICALmedium confidence
- EG Risk
- 44EG Risk 44/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity98% × 45%Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.5% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.5%
- EPSS %ILE
- 39th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
December 28, 2023
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Oct 12, 2026SQL Injection in explain DB queries. · Advisory · LycheeOrg/Lychee · GitHub
https://github.com/LycheeOrg/Lychee/security/advisories/GHSA-rjwv-5j3m-p5x4commit 33354a2ce7cf (LycheeOrg/Lychee)
Patch available: LycheeOrg/Lychee v7.3.1 (contains commit 33354a2ce7cf)
https://github.com/LycheeOrg/Lychee/commit/33354a2ce7cf700cc4ee537b7b8b94dfc1e84ad4Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 35× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 90 of 202 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 10 repeat rows among the latest 100 are merged into the row they repeat. The 112 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-22 23:42 UTCEG score recompute
- 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-21 22:36 UTCEG score recompute
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-20 21:30 UTCEG score recompute
- 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-18 07:43 UTCEG score recompute
- 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-12 18:13 UTCEG score recompute
- 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-12 08:24 UTCOSV refresh
- 2026-10-11 21:39 UTCEG score recompute
- 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.5% · 38th percentile
Show 65 moreShow fewer
- 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-30 16:36 UTCEG score recompute
- 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-22 12:15 UTCOSV refresh
- 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-03 09:29 UTCOSV refresh
- 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-24 14:14 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-16 22:56 UTCOSV refresh
- 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-10 23:57 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-08-01 16:36 UTCOSV refresh
- 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.5% · 38th percentile
Related CVEs(same CWE)
Same CWE
10 shownCWE-89
Frequently asked(5)
What is CVE-2023-52082?
When was the CVE record for CVE-2023-52082 published?
Is CVE-2023-52082 actively exploited?
What is the CVSS score of CVE-2023-52082?
How do I remediate CVE-2023-52082?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2023-52082
Is Your Infrastructure Affected by CVE-2023-52082?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.