599853959f
13 changes to exploits/shellcodes/ghdb Tenda FH451 1.0.0.9 Router - Stack-based Buffer Overflow Discourse 3.1.1 - Unauthenticated Chat Message Access Pie Register WordPress Plugin 3.7.1.4 - Authentication Bypass to RCE Simple File List WordPress Plugin 4.2.2 - File Upload to RCE Joomla JS Jobs plugin 1.4.2 - SQL injection LiveHelperChat 4.61 - Stored Cross Site Scripting (XSS) via Department Assignment Alias Nick Field LiveHelperChat 4.61 - Stored Cross Site Scripting (XSS) via Facebook Integration Page Name Field LiveHelperChat 4.61 - Stored Cross Site Scripting (XSS) via Operator Surname LiveHelperChat 4.61 - Stored Cross Site Scripting (XSS) via Personal Canned Messages LiveHelperChat 4.61 - Stored Cross Site Scripting (XSS) via Telegram Bot Username LiveHelperChat 4.61 - Stored Cross Site Scripting (XSS) via the Chat Transfer Function Microsoft Edge Windows 10 Version 1511 - Cross Site Scripting (XSS)
33 lines
No EOL
1.3 KiB
Text
33 lines
No EOL
1.3 KiB
Text
# Exploit Title: LiveHelperChat 4.61 - Stored Cross Site Scripting (XSS) via Operator Surname
|
|
# Date: 09/06/2025
|
|
# Exploit Author: Manojkumar J (TheWhiteEvil)
|
|
# Linkedin: https://www.linkedin.com/in/manojkumar-j-7ba35b202/
|
|
# Vendor Homepage: https://github.com/LiveHelperChat/livehelperchat/
|
|
# Software Link:
|
|
https://github.com/LiveHelperChat/livehelperchat/
|
|
# Version: <=4.61
|
|
# Patched Version: 4.61
|
|
# Category: Web Application
|
|
# Tested on: Mac OS Sequoia 15.5, Firefox
|
|
# CVE : CVE-2025-51397
|
|
# Exploit link: https://github.com/Thewhiteevil/CVE-2025-51397
|
|
|
|
A stored cross-site scripting (XSS) vulnerability in Live Helper Chat
|
|
version ≤ 4.61 allows attackers to execute arbitrary JavaScript by
|
|
injecting a crafted payload into the Operator Surname field. This payload
|
|
is stored and later executed when an admin or higher-privileged user views
|
|
the Recipients List where the attacker is listed as the Owner.
|
|
|
|
## Reproduction Steps:
|
|
|
|
1. Log in as an operator.
|
|
2. Navigate to your Operator Surname field.
|
|
3. Create new Operator Surname or Modify the Operator Surname, enter the
|
|
following payload:
|
|
```
|
|
"><img src="x" onerror="prompt(1);">
|
|
```
|
|
4. Save the changes.
|
|
5. This payload is stored and later executed when an admin or
|
|
higher-privileged user views the Recipients List where the attacker is
|
|
listed as the Owner. |