dbcve.org
HoteldruidApplication · Digitaldruid

CVE-2025-25748

HIGH · 7.3 CVSS v3.1 Published 2025-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

CSRF vulnerability in HotelDruid 3.0.7's gestione_utenti.php endpoint allows attackers to trick authenticated users into performing unauthorized actions like password modifications due to missing origin/referer validation and absent CSRF token protection. The vulnerability is disputed as the vendor claims an id_sessione CSRF token exists, suggesting the token may not be properly validated.

MitigationImplement proper CSRF token validation (or fix validation of existing id_sessione) and add origin/referer header checks for all state-changing operations in gestione_utenti.php.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HoteldruidApplication
Affected:= 3.0.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm HotelDruid version 3.0.7 is installed
    Locate the HotelDruid installation directory and check version.php or any version file within the application root. Common paths include /var/www/html/hoteldruid/ or check the admin dashboard for version information.
    Affected if The installed version is exactly 3.0.7
  2. Verify gestione_utenti.php endpoint exists
    Navigate to the gestione_utenti.php file within the HotelDruid installation directory (typically in the main application folder). Confirm the file is present and accessible via web browser.
    Affected if The file gestione_utenti.php exists in the deployment
  3. Inspect CSRF token implementation in gestione_utenti.php
    Open gestione_utenti.php in a text editor and search for 'id_sessione' token handling code. Check if a CSRF token is generated, stored in session, and validated before state-changing operations like password modifications.
    Affected if No id_sessione token is generated or the token is not validated before processing requests
  4. Check for origin/referer header validation
    Review the source code of gestione_utenti.php for any $_SERVER['HTTP_ORIGIN'] or $_SERVER['HTTP_REFERER'] validation logic before executing state-changing functions.
    Affected if No origin or referer header validation exists in the code
  5. Test for CSRF vulnerability manually (if authorized)
    Create a proof-of-concept HTML form that submits a password change request to gestione_utenti.php from an external domain, then verify whether the request succeeds without proper CSRF protection.
    Affected if The request succeeds without requiring a valid CSRF token or checking request origin

A user is affected if running HotelDruid version 3.0.7 AND the gestione_utenti.php endpoint lacks proper CSRF token validation AND does not validate origin/referer headers before allowing password modifications.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper CSRF token validation (or fix validation of existing id_sessione) and add origin/referer header checks for all state-changing operations in gestione_utenti.php.

Fix this in Hoteldruid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25748 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-25748 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data