CVE-2025-10759VulnerabilityPublished 21 Sep 2025Updated 22 Sep 2025

CVE-2025-10759: Webkul QloApps · Authorization Bypass

Affects Webkul QloAppsSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Webkul QloApps	Affected =1.0 =1.1 =1.2 =1.3 =1.4 =1.5 =1.6 =1.7.0	Fixed in–

AI-suggested

Given the absence of an official patch, European organizations should implement immediate compensating controls. These include: 1) Restricting network access to the QloApps management interfaces by IP whitelisting or VPN-only access to reduce exposure to remote attackers. 2) Implementing Web Application Firewall (WAF) rules to detect and block suspicious requests with manipulated CSRF tokens or abnormal request patterns targeting QloApps endpoints. 3) Monitoring logs for unusual activities indicative of authorization bypass attempts, such as unexpected changes or access patterns. 4) Temporarily disabling or limiting functionalities that rely on the vulnerable CSRF token handler if feasible. 5) Planning and testing an upgrade path to the next major QloApps release once the vendor releases the patch. 6) Educating staff to recognize and report anomalies in booking or administrative operations that may indicate exploitation. These targeted mitigations go beyond generic advice by focusing on access control hardening, active detection, and operational awareness specific to this vulnerability.

Description

A vulnerability was detected in Webkul QloApps up to 1.7.0. This affects an unknown function of the component CSRF Token Handler. Performing manipulation of the argument token results in authorization bypass. The attack may be initiated remotely. The exploit is now public and may be used. The vendor explains: "As We are already aware about this vulnerability and our Internal team are already working on this issue. (...) We'll implement the fix for this vulnerability in our next major release."

Impact

For European organizations, especially those in the hospitality sector using QloApps for hotel and accommodation management, this vulnerability poses a significant risk. Unauthorized access or actions could lead to manipulation of booking data, financial fraud, disruption of reservation services, and damage to customer trust. Since the vulnerability does not require authentication, attackers can exploit it remotely, increasing the attack surface. The integrity of booking and customer data could be compromised, potentially violating data protection regulations such as GDPR if personal data is altered or exposed indirectly. Operational disruptions could affect service availability indirectly by causing administrative confusion or forcing emergency downtime to mitigate attacks. The medium severity reflects the limited impact on confidentiality and availability but highlights the risk to data integrity and business processes critical to hospitality operations.

Summary

CVE-2025-10759 is a medium-severity authorization bypass vulnerability affecting Webkul's QloApps versions up to 1.7.0. QloApps is a hotel booking and reservation management system widely used by hospitality businesses. The vulnerability arises from improper handling of the CSRF (Cross-Site Request Forgery) token parameter within an unspecified function of the CSRF Token Handler component. By manipulating the token argument, an attacker can bypass authorization controls remotely without requiring authentication or user interaction. This means that an attacker can potentially perform actions or access resources that should be restricted, undermining the integrity of access controls. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P) indicates that the attack can be executed remotely over the network with low complexity, no privileges, and no user interaction, causing a low impact on integrity but no impact on confidentiality or availability. The vulnerability is publicly disclosed, and although no known exploits are reported in the wild yet, the availability of public exploit code increases the risk of exploitation. Organizations using affected versions remain exposed to potential attacks that could allow unauthorized actions within the QloApps system, potentially leading to fraudulent bookings, unauthorized data modifications, or other malicious activities.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Sep 2025, 00:44 UTC

Technical details

References

Community reviews

Related threats