CVE-2025-7435VulnerabilityPublished 11 Jul 2025

CVE-2025-7435: LiveHelperChat lhc-php-resque Extension · Cross Site Scripting

Affects LiveHelperChat lhc-php-resque ExtensionSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/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: Low
User Interaction: Passive
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
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 11 Jul 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-25.

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

AI-suggested

Organizations should promptly apply the patch identified by commit hashes 542aa8449b5aa889b3a54f419e794afe19f56d5d and 0ce7b4f1193c0ed6c6e31a960fafededf979eef2 to remediate the vulnerability. Since the product uses rolling releases, it is critical to track the LiveHelperChat repository for updates continuously. Additionally, administrators should implement strict input validation and output encoding on all user-supplied data, especially the 'queue name' parameter, to prevent script injection. Employing Content Security Policy (CSP) headers can help mitigate the impact of any residual XSS vectors by restricting the execution of unauthorized scripts. Restrict access to the /site_admin/lhcphpresque/list/ interface to trusted IP addresses or via VPN to reduce exposure. Regularly audit and monitor web application logs for suspicious activity indicative of XSS exploitation attempts. Educate users and administrators about the risks of clicking on untrusted links or interacting with unexpected content within the chat system. Finally, integrate vulnerability management processes that include continuous monitoring for new patches and security advisories related to LiveHelperChat.

Description

A vulnerability was found in LiveHelperChat lhc-php-resque Extension up to ee1270b35625f552425e32a6a3061cd54b5085c4. It has been classified as problematic. This affects an unknown part of the file /site_admin/lhcphpresque/list/ of the component List Handler. The manipulation of the argument queue name leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The identifier of the patch is 542aa8449b5aa889b3a54f419e794afe19f56d5d/0ce7b4f1193c0ed6c6e31a960fafededf979eef2. It is recommended to apply a patch to fix this issue.

Impact

For European organizations using LiveHelperChat with the vulnerable lhc-php-resque extension, this XSS vulnerability poses a moderate risk. Exploitation could lead to theft of session tokens or credentials, enabling attackers to impersonate legitimate users or administrators. This could result in unauthorized access to sensitive customer support data, internal communications, or user information, impacting confidentiality and integrity. Since LiveHelperChat is often integrated into customer service workflows, a successful attack could also damage organizational reputation and customer trust. The vulnerability's remote exploitability without authentication increases risk, especially for organizations exposing the admin interface or chat system to the internet. However, the requirement for user interaction and the medium CVSS score suggest the threat is not critical but still significant. European organizations with regulatory obligations under GDPR must consider the potential data breach implications and ensure timely patching to avoid compliance issues. The rolling release nature of the product means organizations must maintain vigilant update practices to mitigate this and future vulnerabilities.

Summary

CVE-2025-7435 is a cross-site scripting (XSS) vulnerability identified in the lhc-php-resque extension of LiveHelperChat, a popular open-source live chat support system. The vulnerability exists in the List Handler component, specifically within the /site_admin/lhcphpresque/list/ file. The flaw arises from improper sanitization of the 'queue name' argument, which can be manipulated by an attacker to inject malicious scripts. This vulnerability can be exploited remotely without requiring authentication, although some user interaction is necessary (e.g., an administrator or user viewing a crafted page). The vulnerability is classified as 'problematic' and has a CVSS 4.0 base score of 5.1, indicating a medium severity level. The attack vector is network-based with low attack complexity and no privileges required, but user interaction is needed. The impact primarily affects confidentiality and integrity to a limited extent, with no direct impact on availability. The product uses a rolling release model, so exact affected versions are identified by commit hashes rather than traditional version numbers. A patch has been issued to address the issue, identified by specific commit hashes, but no direct patch links are provided. No known exploits are currently in the wild, but public disclosure means attackers could develop exploits. The vulnerability allows attackers to execute arbitrary JavaScript in the context of the affected web application, potentially leading to session hijacking, credential theft, or unauthorized actions within the LiveHelperChat admin interface or user sessions.

References

Community reviews

Loading reviews…