Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-10340: Cross Site Scripting in WhatCD Gazelle

0
Medium
VulnerabilityCVE-2025-10340cvecve-2025-10340
Published: Sat Sep 13 2025 (09/13/2025, 02:32:05 UTC)
Source: CVE Database V5
Vendor/Project: WhatCD
Product: Gazelle

Description

A vulnerability was determined in WhatCD Gazelle up to 63b337026d49b5cf63ce4be20fdabdc880112fa3. The affected element is an unknown function of the file /sections/tools/managers/change_log.php of the component Commit Message Handler. Executing manipulation of the argument Message can lead to cross site scripting. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed.

AI-Powered Analysis

AILast updated: 09/21/2025, 00:36:51 UTC

Technical Analysis

CVE-2025-10340 is a cross-site scripting (XSS) vulnerability identified in the WhatCD Gazelle software, specifically affecting the Commit Message Handler component within the file /sections/tools/managers/change_log.php. The vulnerability arises from improper sanitization or validation of the 'Message' argument, which can be manipulated by an attacker to inject malicious scripts. This flaw allows remote attackers to execute arbitrary JavaScript in the context of the victim's browser when they view the affected page. The vulnerability does not require authentication (PR:L means privileges required are low) but does require user interaction (UI:P), such as clicking a crafted link or viewing a manipulated page. The CVSS 4.0 base score is 5.1, indicating a medium severity level. The attack vector is network-based (AV:N), with low attack complexity (AC:L), no privileges required (PR:L), and no user interaction needed for the attack to be initiated, but user interaction is needed for the exploit to succeed. The vulnerability impacts confidentiality and integrity to a limited extent (VC:N, VI:L), with no impact on availability. The product uses a rolling release system, so specific versioning details for patched releases are not disclosed. Although the exploit has been publicly disclosed, there are no known exploits in the wild at this time. The vulnerability could be leveraged to steal session cookies, perform actions on behalf of users, or conduct phishing attacks within the affected application environment.

Potential Impact

For European organizations using WhatCD Gazelle, particularly those managing private torrent or file-sharing communities, this vulnerability could lead to unauthorized script execution in users' browsers. This may result in session hijacking, credential theft, or unauthorized actions performed under the guise of legitimate users. While the direct impact on critical infrastructure is limited, the compromise of user accounts or leakage of sensitive information could damage organizational reputation and user trust. Additionally, if the platform is used for sharing sensitive or proprietary content, the integrity and confidentiality of that data could be at risk. The medium severity rating suggests that while the vulnerability is not catastrophic, exploitation could facilitate further attacks or social engineering campaigns targeting European users. Given the remote attack vector and low complexity, attackers could exploit this vulnerability at scale if the platform is widely used within European communities.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should prioritize applying any available patches or updates from the WhatCD Gazelle project, even though specific version information is not disclosed due to the rolling release model. In the absence of an official patch, organizations should implement strict input validation and output encoding on the 'Message' parameter within the change_log.php component to neutralize malicious scripts. Employing Content Security Policy (CSP) headers can help restrict the execution of unauthorized scripts in browsers. Additionally, organizations should conduct regular security audits and penetration testing focused on XSS vulnerabilities. User education on recognizing phishing attempts and suspicious links can reduce the risk of successful exploitation. Monitoring web application logs for unusual input patterns or error messages related to the change_log.php page can help detect attempted attacks early. Finally, consider implementing web application firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting this specific endpoint.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-09-12T09:00:36.415Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68c4dcd46da8ad0abf38e5f3

Added to database: 9/13/2025, 2:54:12 AM

Last enriched: 9/21/2025, 12:36:51 AM

Last updated: 10/29/2025, 8:13:52 PM

Views: 52

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats