Script execution via unescaped username cookie
Published Aug 26, 2024 · Updated Jul 5, 2026
Cross-site scripting in Gazelle commit 63b3370 allows remote attackers to execute scripts in a user’s browser through a crafted username cookie. The login/disabled.php form writes the username cookie directly into a hidden input value without filtering or output encoding. A user must load the disabled-login page with the cookie set, allowing injected HTML or script to run in that page’s origin.
Summary
What happened
Cross-site scripting in Gazelle commit 63b3370 allows remote attackers to execute scripts in a user’s browser through a crafted username cookie. The login/disabled.php form writes the username cookie directly into a hidden input value without filtering or output encoding. A user must load the disabled-login page with the cookie set, allowing injected HTML or script to run in that page’s origin.
The record
- CVE
- CVE-2024-44795
- Published
- Aug 26, 2024
- Updated
- Jul 5, 2026
- Vendor
- Gazelle Project
- Product
- Gazelle
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 26, 2024CVE publishedPublication date reported by the CVE source.
- Jul 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=commit_63b3370
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Gazelle username-cookie XSS proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo