dbcve.org
QloappsApplication · Webkul

CVE-2025-67325

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-08
Fix available
A fix is available. Upgrade to after 1.7.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unrestricted file upload in the hotel review feature in QloApps versions 1.7.0 and earlier allows remote unauthenticated attackers to achieve remote code execution.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

QloApps versions 1.7.0 and earlier contain an unrestricted file upload vulnerability in the hotel review feature. Remote unauthenticated attackers can upload malicious files (such as PHP web shells) and execute arbitrary code on the server, achieving full remote code execution due to insufficient file type validation, storage location, and execution prevention controls.

MitigationImplement strict allowlist-based file validation (MIME type and extension), store uploads outside the webroot or in non-executable directories, rename uploaded files to prevent direct access, and remove executable permissions. Consider requiring authentication for the review upload functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
QloappsApplication
Affected:<= 1.7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Qloapps installation and version
    Locate the Qloapps installation directory and check the version file or composer.json to determine if the installed version is 1.7.0 or earlier
    Affected if The installed version is 1.7.0 or any version up to 1.7.0
  2. Verify hotel review feature is enabled
    Check the Qloapps admin panel or configuration files to determine if the hotel review and rating module is currently active
    Affected if The hotel review feature is enabled and accessible to users
  3. Inspect upload directory configuration
    Examine the web server configuration and Qloapps upload settings to determine where files uploaded via the review feature are stored
    Affected if Uploaded files are stored within the webroot or in a directory that allows direct URL access
  4. Check file type validation settings
    Review the upload handling code or admin configuration to see what file types are allowed for review attachments
    Affected if File validation is missing, incomplete, or uses only client-side checks without server-side allowlist validation for MIME type and extension
  5. Verify uploaded files have execution prevention
    Check file system permissions on the upload directory and inspect if uploaded files retain executable extensions or can be accessed directly as scripts
    Affected if Uploaded files can be accessed via URL and are executed as server-side scripts (e.g., .php files are directly accessible and executed)

A user is affected if they are running Qloapps version 1.7.0 or earlier with the hotel review feature enabled, and uploads are stored in a publicly accessible location without proper file type validation or execution prevention.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.7.0
Interim mitigation

Implement strict allowlist-based file validation (MIME type and extension), store uploads outside the webroot or in non-executable directories, rename uploaded files to prevent direct access, and remove executable permissions. Consider requiring authentication for the review upload functionality.

Recommended fix Moderate confidence

Qloapps 1.7.1 or later stable release (check GitHub releases for latest)

  1. 1. Backup the current Qloapps installation and database before making any changes.
  2. 2. Navigate to the official QloApps GitHub repository at github.com/quantacode/qloapps
  3. 3. Check the releases or tags section to identify the latest stable version beyond 1.7.0
  4. 4. Download the latest release package from the repository
  5. 5. Replace the existing installation files with the new version, preserving configuration and custom files
  6. 6. Verify the hotel review upload functionality now properly validates file types (e.g., only allows images like jpg, png)
  7. 7. Confirm file uploads are stored outside the web root or with non-executable extensions
  8. 8. Test that PHP or other executable files can no longer be uploaded through the review feature
Caveat Review changelog for any template or customization changes between versions that may affect hotel booking customizations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Qloapps Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-67325 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data