CVE-2025-53839: dracoon security-advisories · Cross-site Scripting
Affects dracoon security-advisoriesSource CVE Database V5
Not known to be exploited · CVSS 4.0 Medium : upgrade to 2.10.0 when convenient.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.10.0
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 14 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 26 Oct 2026.
What to do
Upgrade dracoon/security-advisories to 2.10.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubdracoon/security-advisoriespkg:github/dracoon/security-advisoriesOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations should ensure that all instances of the DRACOON Branding Service are updated to version 2.10.0 or later, where the vulnerability is fixed. Since the vendor has rolled out the patch to the DRACOON service, customers using the cloud-hosted version may already be protected, but on-premises deployments must be verified and updated promptly. Additionally, organizations should enforce strict administrative account management policies, including the use of multi-factor authentication (MFA), least privilege principles, and regular auditing of administrative actions. Monitoring onboarding workflows for anomalous behavior or unexpected HTML/script content can help detect exploitation attempts. Web application firewalls (WAFs) configured to detect and block XSS payloads may provide an additional layer of defense. User training to recognize suspicious activities during onboarding can also reduce the risk of successful exploitation. Finally, organizations should review and tighten input validation and output encoding practices in any custom branding or interface customization to prevent similar vulnerabilities.
Description
DRACOON is a file sharing service, and the DRACOON Branding Service allows customers to customize their DRACOON interface with their brand. Versions of the DRACOON Branding Service prior to 2.10.0 are vulnerable to cross-site scripting. Improper neutralization of input from administrative users could inject HTML code into the workflow for newly onboarded users. A fix was made available in version 2.10.0 and rolled out to the DRACOON service. DRACOON customers do not need to take action.