CVE-2026-33644 | Lychee up to 7.5.1 Domain Name PhotoUrlRule.php filter_var host server-side request forgery (GHSA-5245-4p8c-jwff)

VDB-353753 · CVE-2026-33644 · GHSA-5245-4P8C-JWFF LYCHEE UP TO 7.5.1 DOMAIN NAME PHOTOURLRULE.PHP FILTER_VAR HOST SERVER-SIDE REQUEST FORGERY HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.0 $0-$5k 1.29+ Summaryinfo A vulnerability, which was classified as critical, has been found in Lychee up to 7.5.1. This issue affects the function filter_var of the file PhotoUrlRule.php of the component Domain Name Handler. The manipulation of the argument host leads to server-side request forgery. This vulnerability is listed as CVE-2026-33644. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component. Detailsinfo A vulnerability was found in Lychee up to 7.5.1. It has been rated as critical. This issue affects the function filter_var of the file PhotoUrlRule.php of the component Domain Name Handler. The manipulation of the argument host with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality, integrity, and availability. The summary by CVE is: Lychee is a free, open-source photo-management tool. Prior to version 7.5.2, the SSRF protection in `PhotoUrlRule.php` can be bypassed using DNS rebinding. The IP validation check (line 86-89) only activates when the hostname is an IP address. When a domain name is used, `filter_var($host, FILTER_VALIDATE_IP)` returns `false`, skipping the entire check. Version 7.5.2 patches the issue. The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-33644 since 03/23/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. By approaching the search of inurl:PhotoUrlRule.php it is possible to find vulnerable targets with Google Hacking. Upgrading to version 7.5.2 eliminates this vulnerability. Applying the patch 28c5261fb9deab4f9420c8cc2f73a87425939107 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Name Lychee Version 7.5.0 7.5.1 License open-source CPE 2.3info 🔒 🔒 CPE 2.2info 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 6.3 VulDB Meta Temp Score: 6.0 VulDB Base Score: 6.3 VulDB Temp Score: 6.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Server-side request forgery CWE: CWE-918 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Google Hack: 🔒 Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: Lychee 7.5.2 Patch: 28c5261fb9deab4f9420c8cc2f73a87425939107 Timelineinfo 03/23/2026 CVE reserved 03/26/2026 +3 days Advisory disclosed 03/26/2026 +0 days VulDB entry created 03/26/2026 +0 days VulDB entry last update Sourcesinfo Advisory: GHSA-5245-4p8c-jwff Status: Confirmed CVE: CVE-2026-33644 (🔒) GCVE (CVE): GCVE-0-2026-33644 GCVE (VulDB): GCVE-100-353753 Entryinfo Created: 03/26/2026 23:12 Changes: 03/26/2026 23:12 (72) Complete: 🔍 Cache ID: 99:3D5:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸