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

Back
New CVE Detected

CVE-2026-65694 – Arbitrary File Read via Path Traversal – Microweber CMS through 2.0.20

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-65694 is a high-severity path traversal vulnerability (CWE-22) in Microweber CMS affecting all versions through 2.0.20. The flaw allows unauthenticated remote attackers to read arbitrary files from the server — including sensitive .env configuration files — by sending a single HTTP GET request. It carries a CVSS 4.0 score of 8.7 (HIGH).

Technical details

  • Root cause: The ServeStaticFileController::serveFromUserfiles() method reads the file path from the $request->path query parameter instead of the bound route parameter $request->route('path'). This allows a ?path= query string to override the intended route segment. The normalize_path() function subsequently fails to strip directory traversal sequences (../), enabling path escape outside the intended userfiles directory.
  • Trigger conditions: No authentication, no user interaction, and no special configuration are required. A single crafted HTTP GET request to the static file controller endpoint is sufficient to trigger the vulnerability.
  • Attack vector: Unauthenticated remote network access via HTTP GET request containing directory traversal sequences in the path query parameter (e.g., ?path=../../.env).
  • Impact: Arbitrary file read with high confidentiality impact. Sensitive targets include .env files (exposing database credentials, API keys, and application secrets) and system files. Successful exploitation can serve as a direct stepping stone to full system compromise.

Affected software

  • Microweber CMS — all versions through 2.0.20 (inclusive)

Severity

  • CVSS 4.0: 8.7 (HIGH) — 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
  • CVSS 3.1: 7.5 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Patch status: A fix has been proposed in GitHub Pull Request #1181, which updates the controller to use $request->route('path'), applies realpath() canonicalization, and enforces that the resolved path remains within the userfiles_path() directory. As of the publication of this advisory, the fix has not yet been merged into the main branch and no patched release is available.
  • Immediate workaround — restrict access at the network perimeter: Where possible, place Microweber instances behind a WAF or reverse proxy configured to block requests containing directory traversal sequences (../, ..%2F, %2e%2e/) in query parameters.
  • Immediate workaround — limit file system exposure: Ensure the web server process runs under a least-privilege account with read access restricted to application directories only, reducing the scope of files reachable via traversal.
  • Monitor: Track the upstream repository for the official patched release and apply it immediately upon availability.

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

  • 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