CVE-2025-65132
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 · uneditedalandsilva26 hotel-management-php 1.0 is vulnerable to Cross Site Scripting (XSS) in /public/admin/edit_room.php which allows an attacker to inject and execute arbitrary JavaScript via the room_id GET parameter.
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 · high confidenceThe hotel-management-php application version 1.0 contains a reflected XSS vulnerability in /public/admin/edit_room.php. The room_id GET parameter is not properly sanitized before being reflected in the HTML output, allowing an attacker to inject arbitrary JavaScript that executes in the context of a victim's browser session.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 hotel-management-php installationSearch the web server document root for the hotel-management-php directory or check for the presence of edit_room.php in the /public/admin/ pathAffected if The application is installed and the file /public/admin/edit_room.php exists on the server
-
Confirm application versionCheck for a version file, composer.json, or any version indicator within the hotel-management-php installation directoryAffected if The installed version is 1.0 (the only affected version listed)
-
Inspect the edit_room.php fileOpen /public/admin/edit_room.php and search for the room_id parameter handling (look for $_GET['room_id'] or similar)Affected if The file processes the room_id GET parameter without sanitization
-
Check for output encoding on room_idSearch the edit_room.php file for htmlspecialchars(), htmlentities(), or other encoding functions applied to the room_id value before HTML outputAffected if The room_id parameter is echoed directly to HTML without encoding functions like htmlspecialchars()
-
Test the parameter if possibleIf you have a test environment, send a request to /public/admin/edit_room.php?room_id=<script>alert(1)</script> and verify whether the script tag appears unencoded in the responseAffected if The payload is reflected unchanged in the HTML response, confirming the XSS vulnerability
You are affected if hotel-management-php version 1.0 is installed and the /public/admin/edit_room.php file reflects the room_id GET parameter without sanitization or output encoding.
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 proper input validation and output encoding for the room_id parameter. All user-supplied input must be sanitized before rendering in HTML using functions like htmlspecialchars() or a context-appropriate encoding library.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65132 — 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-65132 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