# CVE-2025-53839: DRACOON Branding Service vulnerable to Cross-site Scripting

> Administrative users can inject HTML into the onboarding workflow, potentially compromising newly onboarded users in DRACOON.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jul 2025
- **Updated:** 15 Jul 2025

## What is CVE-2025-53839?

CVE-2025-53839 is a medium-severity cross-site scripting vulnerability in dracoon security-advisories, published on 14 Jul 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-53839?


## How do I fix CVE-2025-53839?

No fix has been published for CVE-2025-53839 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-53839 being exploited?

There is no known exploitation of CVE-2025-53839 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53839 and fix it if it is affected.

What it is: CVE-2025-53839 is a medium-severity cross-site scripting vulnerability in dracoon security-advisories, published on 14 Jul 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-53839 in the wild and no public exploit code.

Affected product: dracoon security-advisories. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53839/ (Markdown: https://insights.sbomify.com/CVE-2025-53839/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53839
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53839
- OSV: https://osv.dev/vulnerability/CVE-2025-53839

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53839/
Summaries are generated and may contain mistakes; the official description above is the record.