CVE-2026-109393
6.3MediumPublished 12 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Impact
- Limited impact
- Weakness
- CWE-639
Impact
Authenticated back-office employees can access, upload, and delete booking documents, rooms, and images belonging to other hotels. Attackers need valid employee credentials with hotel-restricted access to the back-office.
Root cause
Multiple back-office AJAX controllers fail to validate hotel-level permissions ('htl_access') when processing sequential IDs in requests.
Affected systems
QloApps through version 1.7.0
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Fix & remediation
Upgrade to a version containing commit 83eb851cf106b51a4478f84a6d1658d7c8076258 (Pull Request #1922) once released. As an interim workaround, restrict or suspend multi-tenant employee accounts that should not have cross-hotel access.
$ git pull origin masterAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
QloApps through 1.7.0 contains an insecure direct object reference vulnerability in back-office AJAX handlers of AdminOrdersController, AdminBookingDocumentController, AdminProductsController and AdminAddHotelController that skip htl_access hotel checks. Hotel-restricted employees can supply other hotels' sequential identifiers to read, upload and delete booking documents and delete rooms, room images and hotel images.
References
- https://github.com/Qloapps/QloApps
- https://github.com/Qloapps/QloApps/blob/v1.7.0/controllers/admin/AdminOrdersController.php#L3799-L3877
- https://github.com/Qloapps/QloApps/commit/83eb851cf106b51a4478f84a6d1658d7c8076258
- https://github.com/Qloapps/QloApps/pull/1922
- https://hackmd.io/@leediay/ry_M5yqoGe
- https://www.vulncheck.com/advisories/qloapps-through-1.7.0-insecure-direct-object-reference-in-back-office-ajax-handlers