Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-9506 – Unauthenticated Arbitrary File Read – Bagisto v2.4.1

Be the first to know when new zero-days emerge:

Summary

CVE-2026-9506 is a path traversal vulnerability (CWE-22) in the ImageCacheController component of Bagisto, an open-source Laravel eCommerce platform developed by Webkul. An unauthenticated remote attacker can supply crafted path traversal sequences via the filename parameter to read arbitrary files outside the intended directory on the server. The vulnerability carries a CVSS 4.0 base score of 8.7 (HIGH) and requires no credentials, no prerequisites, and no user interaction to exploit.

Technical details

  • Root cause: Improper validation of user-supplied input in the ImageCacheController component (part of the bagisto/image-cache package). The controller, which is designed to serve cached images to unauthenticated storefront visitors, does not adequately sanitise or restrict the filename parameter before using it to locate a file on the filesystem.
  • Trigger conditions: An attacker sends a crafted HTTP request to the image-caching endpoint containing path traversal sequences (e.g. ../) in the filename parameter. No session or authentication token is required.
  • Attack vector: Network-accessible; the endpoint is exposed as part of the public-facing storefront with no authentication gate.
  • Impact: Successful exploitation allows the attacker to read arbitrary files from the server — including the Laravel .env file (which typically contains APP_KEY, database credentials, and payment API keys), application configuration files, and other sensitive data. Exposure of these secrets can enable further privilege escalation or full application compromise.

Affected software

  • Bagisto (by Webkul) — version 2.4.1
  • Earlier versions may also be affected; v2.4.1 is the confirmed vulnerable release per the CERT-In advisory.

Severity

  • CVSS 4.0 Base Score: 8.7 (HIGH)
  • CVSS 4.0 Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate – apply the vendor patch: Upgrade Bagisto to v2.4.2 or later. The fix is available at https://github.com/bagisto/bagisto/tree/v2.4.2. The v2.4.2 release resolves the unauthenticated path traversal via the ImageCache component (issue #11220).
  • If immediate patching is not possible: Restrict access to the image-cache endpoint at the web server or WAF layer to prevent external path traversal requests from reaching the controller. Additionally, ensure the web server process runs under a least-privilege user account to limit the files readable in the event of exploitation.
  • Post-remediation: Treat any .env file contents as potentially compromised; rotate the Laravel APP_KEY, database credentials, and all API keys stored in the environment file.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge