# CVE-2025-63693: Cross-site scripting in n/a

> Attackers can execute arbitrary JavaScript in victims' browsers via unsanitized comment editing templates in DzzOffice.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Nov 2025
- **Updated:** 19 Nov 2025
- **Also known as:** GHSA-5472-qhvw-4r4w

## What is CVE-2025-63693?

CVE-2025-63693 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The comment editing template (dzz/comment/template/edit_form.htm) in DzzOffice 2.3.x lacks adequate security escaping for user-controllable data in multiple contexts, including HTML and JavaScript strings. This allows low-privilege attackers to construct comment content or request parameters and execute arbitrary JavaScript code when the victim opens the editing pop-up.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Dzzoffice Dzzoffice.

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

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

## Is CVE-2025-63693 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-63694](https://insights.sbomify.com/CVE-2025-63694/): SQL injection in n/a (critical 9.8)
- [CVE-2025-63695](https://insights.sbomify.com/CVE-2025-63695/): File upload in n/a (critical 9.8)
- [CVE-2024-41376](https://insights.sbomify.com/CVE-2024-41376/): Path traversal in n/a (high 8.8)
- [CVE-2022-43340](https://insights.sbomify.com/CVE-2022-43340/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2023-39853](https://insights.sbomify.com/CVE-2023-39853/): SQL injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63693 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-63693 in the wild and no public exploit code.

Affected product: n/a. 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-63693/ (Markdown: https://insights.sbomify.com/CVE-2025-63693/index.md)
```

## Sources

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

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