CVE Alert: CVE-2025-9639 – Ai3 – QbiCRMGateway

CVE-2025-9639

HIGHNo exploitation known

The QbiCRMGateway developed by Ai3 has an Arbitrary File Reading vulnerability, allowing unauthenticated remote attackers to exploit Relative Path Traversal to download arbitrary system files.

CVSS v3.1 (7.5)
AV NETWORK · AC LOW · PR NONE · UI NONE · S UNCHANGED
Vendor
Ai3
Product
QbiCRMGateway
Versions
7.5.1 lte 8.5.03
CWE
CWE-23, CWE-23 Relative Path Traversal
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2025-08-29T03:39:35.620Z
Updated
2025-08-29T03:39:35.620Z

AI Summary Analysis

Risk verdict

High risk: unauthenticated remote arbitrary file reading via relative path traversal with external exposure; patch urgently.

Why this matters

Attachers can fetch arbitrary system files, potentially exposing credentials or sensitive configuration. Combined with network-facing access, this can enable data leakage, disclosure of secrets, or groundwork for further compromise with little/no user interaction.

Most likely attack path

Direct, unauthenticated requests over the network to the vulnerable endpoint, exploiting relative path traversal to download files. No privileges required and no user interaction, so attacker can target sensitive files immediately. Scope remains unchanged, but successful reads could facilitate credential or config exposure for further moves.

Who is most exposed

Organisations deploying QbiCRMGateway at the network edge or as an internet-facing API gateway are most at risk; those with external exposure and access to server file systems should prioritise remediation.

Detection ideas

  • Logs showing path traversal patterns (../ or ..\) targeting file download endpoints.
  • Unusual spikes in requests aiming at sensitive file names (e.g., system config or credential files).
  • Increased outbound data transfers following such requests.
  • WAF/IPS alerts for traversal attempts across gateway endpoints.
  • Anomalous 200 responses returning file-like content to unauthenticated clients.

Mitigation and prioritisation

  • Patch to v8.5.04 or later immediately.
  • If patching is delayed, deploy compensating controls (Web Application Firewall rules to block path traversal; restrict file-system access; disable directory listing).
  • Implement input validation/sanitisation and a strict allowlist for permissible file access; review code paths handling file reads.
  • Apply least-privilege and network segmentation; monitor and alert on suspicious file access activity.
  • If KEV is true or EPSS ≥ 0.5, treat as priority 1. If those indicators are not available, still prioritise within your standard change window given external exposure.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below

To keep up to date follow us on the below channels.