Skip to main content
VulnerabilityPublished Updated

CVE-2025-10340: WhatCD Gazelle · Cross-site Scripting

Affects WhatCD GazelleSource CVE Database V5

0

Public exploit available · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 10:12 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 17% 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

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.

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.

References

Community reviews

Loading reviews…