Bagisto EUVD-2026-24241

Exploitation requires valid Bagisto user authentication (PR:L in CVSS vector) - the attacker must possess a legitimate account or have compromised one. The Downloadable Link Handler component and specifically its copy function must be accessible in the target Bagisto deployment. No other special configuration or non-default settings are explicitly mentioned in the description, suggesting the vulnerability is exploitable against standard Bagisto installations with user accounts enabled. Network access to the Bagisto application endpoint is required (AV:N confirmed by CVSS). The impact is further constrained by CVSS showing no scope change (SC:N) and only low confidentiality/integrity impact (VC:L/VI:L/VA:L), meaning the attacker's view of sensitive data is limited to what the server can access in the context of the application process. Limitations: authentication requirement prevents unauthenticated exploitation, and the low-impact ratings suggest the attacker cannot directly execute code or fully compromise the application itself, only exfiltrate or manipulate data accessible via SSRF.

Risk assessment reveals a moderate-risk scenario with important caveats. CVSS score of 5.3 reflects AV:N/AC:L (network-accessible, low complexity) with PR:L (low-privilege authentication required), limiting impact to authenticated users only. The CVSS vector shows low confidentiality (VC:L) and integrity (VI:L) impact with no scope change, indicating the vulnerability is exploitable but with constrained blast radius. EPSS is not provided, preventing quantification of real-world exploitation likelihood. However, POC availability and vendor confirmation of the issue elevate practical concern. The active exploitation status (KEV listing not present in input, but POC is public) suggests this is a known, usable attack vector rather than a critical zero-day. Real-world risk depends heavily on deployment context: internal Bagisto instances or low-risk deployments are less concerning than customer-facing e-commerce platforms with exposed sensitive internal APIs. The low-privilege requirement (authenticated attacker) and constrained impact scope suggest this is not an immediate crisis but warrants prioritization in patching queues for exposed Bagisto deployments.

An attacker with a valid Bagisto user account (e.g., a disgruntled employee or compromised customer account) uses the publicly available exploit code to craft a malicious request to the Downloadable Link Handler copy endpoint, specifying an internal URL such as http://169.254.169.254/latest/meta-data/ (AWS metadata service) or http://internal-api:8080/admin/config. The application processes this request on the server side, retrieves the response, and either returns sensitive data to the attacker or allows enumeration of internal services. A more sophisticated attacker could chain this with cloud credential theft if metadata endpoints are exposed.