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

Back
New CVE Detected

CVE-2026-75594 – Path Traversal / Unauthorized File Access – Kirby CMS < 4.9.5 and 5.0.0–5.5.1

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-75594 is a path traversal vulnerability (CWE-22) in Kirby CMS’s media handling that allows an unauthenticated remote attacker to access image files and detect the existence of JSON files outside the site’s intended media directory. It affects Kirby versions prior to 4.9.5 and 5.0.0 through 5.5.1, and carries a CVSS score of 8.2 (High).

Technical details

  • Root cause: KirbyCmsMedia::thumb() appends attacker-supplied filenames to a validated parent media directory without rejecting path traversal sequences; a related weakness exists in the file::version path handling in Asset, which also accepted ../ sequences.
  • Trigger conditions: exploitation requires a server configuration that permits encoded slash characters in URLs — nginx, PHP’s built-in development server, or Apache with AllowEncodedSlashes enabled. Apache’s default configuration is not affected.
  • Attack vector: network, unauthenticated, low complexity — an attacker submits thumbnail/media requests containing encoded slash (%2f) sequences to traverse outside the parent media directory.
  • Impact: disclosure of image files stored outside the intended media root, and the ability to infer whether arbitrary .json files exist on the server via differences in server responses; a crafted job file could also cause an unintended image to be returned.

Affected software

  • Kirby CMS versions prior to 4.9.5
  • Kirby CMS versions 5.0.0 through 5.5.1 (inclusive)

Severity

  • CVSS v4.0 Base Score: 8.2 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: upgrade to Kirby CMS 4.9.5 (for 4.x deployments) or 5.5.2 (for 5.x deployments) or later, where Media::thumb() rejects filenames containing path traversal sequences and the Asset class/asset() helper reject ../ sequences.
  • If patching is not immediately possible: avoid running Kirby behind server configurations that allow encoded slashes (do not enable AllowEncodedSlashes on Apache; review nginx and PHP built-in server deployments), and restrict direct access to the media handler where feasible until the update can be applied.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Kirby Panel

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge