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

> Attackers can execute arbitrary code and steal sensitive information via a cross-site scripting flaw in the HotelDruid backup creation endpoint.

- **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:** 11 Mar 2025
- **Updated:** 12 Mar 2025
- **Also known as:** DEBIAN-CVE-2025-25747, GHSA-fw35-27g6-hvhf, UBUNTU-CVE-2025-25747

## What is CVE-2025-25747?

CVE-2025-25747 is a medium-severity cross-site scripting vulnerability in n/a, published on 11 Mar 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

Cross Site Scripting vulnerability in DigitalDruid HotelDruid v.3.0.7 allows an attacker to execute arbitrary code and obtain sensitive information via the ripristina_backup parameter in the crea_backup.php endpoint

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

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

It affects 1 product.


Products: Digitaldruid Hoteldruid.

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

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

## Is CVE-2025-25747 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25747 exists.

Public exploit code:

- https://github.com/huyvo2910/CVE-2025-25747-HotelDruid-3-0-7-Reflected-XSS (github_poc): https://github.com/huyvo2910/CVE-2025-25747-HotelDruid-3-0-7-Reflected-XSS

## Other vulnerabilities in n/a

- [CVE-2023-43371](https://insights.sbomify.com/CVE-2023-43371/): SQL injection in n/a (critical 9.8)
- [CVE-2023-43373](https://insights.sbomify.com/CVE-2023-43373/): SQL injection in n/a (critical 9.8)
- [CVE-2023-43374](https://insights.sbomify.com/CVE-2023-43374/): SQL injection in n/a (critical 9.8)
- [CVE-2023-43375](https://insights.sbomify.com/CVE-2023-43375/): SQL injection in n/a (critical 9.8)
- [CVE-2021-42949](https://insights.sbomify.com/CVE-2021-42949/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25747 is a medium-severity cross-site scripting vulnerability in n/a, published on 11 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25747 exists.

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-25747/ (Markdown: https://insights.sbomify.com/CVE-2025-25747/index.md)
```

## Sources

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

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