# CVE-2025-25748: Cross-site request forgery in n/a

> Attackers can perform unauthorized actions like password modification on behalf of authenticated users in HotelDruid due to potential CSRF flaws.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2025
- **Updated:** 21 Mar 2025
- **Also known as:** DEBIAN-CVE-2025-25748, GHSA-r375-j569-v9qr, UBUNTU-CVE-2025-25748

## What is CVE-2025-25748?

CVE-2025-25748 is a high-severity vulnerability in n/a, published on 11 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A CSRF vulnerability in the gestione_utenti.php endpoint of HotelDruid 3.0.7 allows attackers to perform unauthorized actions (e.g., modifying user passwords) on behalf of authenticated users by exploiting the lack of origin or referrer validation and the absence of CSRF tokens. NOTE: this is disputed because there is an id_sessione CSRF token.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Digitaldruid Hoteldruid.

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

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

## Is CVE-2025-25748 being exploited?

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

Public exploit code:

- Cross-Site Request Forgery (CSRF) Vulnerability in HotelDruid 3.0.7 (CVE-2025-25748) (github_poc): https://github.com/huyvo2910/CVE-2525-25748-Cross-Site-Request-Forgery-CSRF-Vulnerability-in-HotelDruid-3.0.7

## 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-25748 and fix it if it is affected.

What it is: CVE-2025-25748 is a high-severity vulnerability in n/a, published on 11 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25748 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-25748/ (Markdown: https://insights.sbomify.com/CVE-2025-25748/index.md)
```

## Sources

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

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