CVE-2025-60168
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in integrationshotelrunner HotelRunner Booking Widget hotelrunner allows Stored XSS.This issue affects HotelRunner Booking Widget: from n/a through <= 1.6.
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 confidenceCSRF vulnerability in HotelRunner Booking Widget allows authenticated attackers to inject Stored XSS payloads via malicious forms or links. When an administrator unknowingly submits the crafted request, malicious scripts are stored in the widget and execute for users viewing the booking page.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate HotelRunner Booking Widget installationSearch web application directories for HotelRunner-related files, folders, or modules. Check for hotelrunner class definitions, widget configuration files, or plugin/theme integrations containing 'hotelrunner' references.Affected if HotelRunner Booking Widget files are present in the environment
-
Determine installed versionExamine version files, composer.json, plugin metadata, or widget footer/version info to identify the exact version number. Compare against any known fixed releases.Affected if Version cannot be determined or falls within vulnerable release ranges
-
Inspect admin forms for CSRF tokensView the HTML source code of admin-facing booking management forms (create/edit booking, widget settings). Look for hidden input fields containing anti-CSRF tokens orSameSite cookie attributes.Affected if Admin forms lack CSRF token validation or SameSite cookie protection
-
Test input sanitization on booking formsSubmit test payloads containing script tags and special characters through booking widget admin forms. Then retrieve and inspect the stored data or view it on the public booking page.Affected if Special characters are stored and rendered without proper encoding or sanitization
-
Verify booking page output encodingAccess the public-facing booking page and use browser developer tools or view page source to inspect whether user-supplied data in forms, links, or content is properly escaped.Affected if Unescaped user input appears in HTML output on booking pages
Environment is affected if HotelRunner Booking Widget is present and either lacks CSRF protections on admin forms or fails to sanitize and encode user inputs before storage and rendering.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement anti-CSRF tokens on all admin-facing forms and validate/sanitize all user inputs before storage and output encoding before rendering.
- Consultation2.0 h
- Implementation5.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60168 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-60168 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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