Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain high-privileged API credentials
-
DeliverySubmit crafted img_url to v1 serializer
-
ExploitServer fetches attacker-controlled URL (SSRF)
-
ExecutionReach internal/restricted resource
-
ImpactRetrieve limited internal response
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated attacker with high privileges (PR:H) on the TiBillet Lespass v1 API, and the ability to supply the img_url or image_url argument to one of the three affected APIv1 serializers that call get_img_from_url. Exploitation is explicitly difficult (AC:H): the server-side fetch lacks destination IP validation, redirect re-checks, and download timeout/size limits, so an attacker must craft URLs (and likely abuse redirects) to reach internal targets. Limiting factors: high-privilege authentication is mandatory, attack complexity is high, impact is Low across C/I/A with no scope change, and the vulnerable v1 endpoints are deprecated and scheduled for removal - reducing the realistic exposure window. |
| Impact | This is a low-priority issue despite being a real, vendor-confirmed vulnerability. The CVSS 4.0 base score of 2.1 is consistent across every signal: the vector (AV:N/AC:H/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L) shows network reachability but high attack complexity, a requirement for high privileges (PR:H), and only Low impact to confidentiality, integrity, and availability with no scope/subsequent-system change. The vendor itself characterizes exploitability as 'difficult.' No EPSS score was provided in the input, there is no CISA KEV listing, and no public exploit (POC) is referenced - so exploitation status is 'no public exploit identified at time of analysis.' The sole source is a VulDB submission (CVE-2026-112358 / vuldb.com/vuln/422393); there is no independent vendor advisory URL, though the vendor statement about a planned v2 fix is quoted. No signals conflict: all of them (low CVSS, high complexity, authenticated-only access, low impacts, no exploitation evidence) point in the same direction. The one caveat is that SSRF class flaws (CWE-918) can sometimes enable higher impact (internal network pivoting, cloud metadata access) than a Low-impact rating suggests, but the quoted vendor mitigations (destination IP validation, redirect re-checks) and the AC:H/PR:H gating make broad exploitation unlikely. Treat as low urgency; the affected v1 API is already slated for removal. |
| Exploit ScenarioDerived | An attacker who already holds a high-privileged authenticated account on a TiBillet Lespass v1 API deployment submits a crafted img_url/image_url value to an APIv1 serializer endpoint, causing the server's get_img_from_url function to fetch an attacker-chosen URL and reach internal services the attacker cannot normally access. Because the vendor rates exploitability as difficult (AC:H) and no destination-IP validation bypass is trivial, the attacker likely needs redirect tricks and careful targeting; impact is limited (Low C/I/A). No public exploit code is referenced at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Server-side request forgery in TiBillet Lespass v1 API allows an authenticated attacker with high privileges to make the server fetch arbitrary URLs supplied through the img_url or image_url argument in the get_img_from_url function, potentially reaching internal services. The vendor confirms the weakness affects versions up to commit 10e87909c5d526dffa6d424c104fc12860740537 and states that destination IP validation, redirect re-checks, and download timeout/size limits are planned for the v2 API. Exploitation is rated difficult (AC:H) and no public exploit was identified at time of analysis; this is a low-priority, vendor-confirmed issue.
RemediationAI
No vendor-released patch for the affected v1 API was identified at time of analysis; the vendor plans destination IP validation, redirect re-checks, and timeout/size limits in the v2 API and will remove the three affected v1 serializers in the next major release. Until then, migrate integrations to the v2 API as it becomes available, restrict v1 API access to trusted high-privilege accounts, and add egress filtering or an HTTP proxy that blocks private, loopback, link-local, and cloud metadata address ranges for server-side image fetches (trade-off: may break legitimate external image imports). Also disable or constrain the remote image download feature if business requirements allow, and enforce short timeouts and response size caps at the network layer. Consult https://vuldb.com/vuln/422393 and https://vuldb.com/cve/CVE-2026-112358 for updates.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-918 (Server-Side Request Forgery) in TiBillet Lespass's Django REST Framework serializers under ApiBillet/serializers.py, where get_img_from_url accepts an img_url/image_url value and performs a server-side HTTP fetch without validating the destination IP, re-checking redirects, or enforcing timeout and size limits. The CVSS 4.0 vector AV:N/AC:H/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X and the independent CVSS 3.1 vector AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L both reflect remote reachability but require high privileges and difficult attack conditions. Because redirects are not re-validated and internal destinations are not blocked, a high-privilege API user could craft URLs that cause the Lespass server to request internal resources, though the low C/I/A impact and lack of scope change limit severity. The CPE cpe:2.3:a:tibillet:lespass:*:*:*:*:*:*:*:* covers Lespass versions through the cited commit.
Know when Lespass gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
Network-reachable but requires high-privileged API auth (PR:H) and is vendor-rated difficult (AC:H); SSRF yields only limited internal access, so Low C/I/A and unchanged scope.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
DescriptionCVE.org
A weakness has been identified in TiBillet Lespass up to 10e87909c5d526dffa6d424c104fc12860740537. This vulnerability affects the function get_img_from_url of the file ApiBillet/serializers.py of the component APIv1. Executing a manipulation of the argument img_url/image_url can lead to server-side request forgery. The attack can be launched remotely. A high complexity level is associated with this attack. It is stated that the exploitability is difficult. The vendor confirms: "[T]he fix (destination IP validation, redirect re-checks, timeout and size limit on remote image download) is already planned in our v2 API, which replaces the affected v1 endpoints. The v1 API, including the three affected serializers, will be removed in our next major release."
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
EUVD-2026-104637
GHSA-jgh9-mwr6-9jc2
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB