CVE Alert: CVE-2025-10623 – SourceCodester – Hotel Reservation System

CVE-2025-10623

HIGHNo exploitation known

A vulnerability was identified in SourceCodester Hotel Reservation System 1.0. The impacted element is an unknown function of the file deleteuser.php. Such manipulation of the argument ID leads to sql injection. It is possible to launch the attack remotely. The exploit is publicly available and might be used.

CVSS v3.1 (7.3)
Vendor
SourceCodester
Product
Hotel Reservation System
Versions
1.0
CWE
CWE-89, SQL Injection
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Published
2025-09-17T22:32:08.211Z
Updated
2025-09-17T22:32:08.211Z

AI Summary Analysis

Risk verdict

High risk: remote SQL injection with publicly available exploit; no authentication required, so prompt action is advised.

Why this matters

Attackers could access, modify, or exfiltrate data tied to reservations, potentially exposing PII and disrupting operations. The public exploit lowers barriers for automated abuse across exposed deployments.

Most likely attack path

An unauthenticated actor targets deleteuser.php via the ID parameter, triggering an injection in the backend query. With network access and low complexity, data leakage, record modification, or service impact within the app’s database is possible, and no user interaction is required. Scope remains within the vulnerable component unless broader DB access exists.

Who is most exposed

Internet-facing installations of SourceCodester Hotel Reservation System 1.0, especially in small to medium organisations running common LAMP stacks.

Detection ideas

  • Look for unusual or repeated requests to deleteuser.php with crafted ID inputs.
  • Monitor web/app logs for SQL syntax errors or database error codes.
  • IDS/WAF alerts matching SQLi patterns or PoC indicators.
  • Anomalous data access around user or booking records.
  • Unscheduled data transfers or spikes in DB query latency tied to the endpoint.

Mitigation and prioritisation

  • Patch or upgrade to a fixed version; if not feasible, apply compensating controls. Treat as priority 2.
  • Enforce parameterised queries and input validation; implement least-privilege DB accounts.
  • Restrict or disable direct access to deleteuser.php (IP allowlists, authentication).
  • Deploy WAF/IDS rules specific to SQLi; tighten logging and alerting for this endpoint.
  • Plan patching in the next maintenance window with backups and post-fix validation.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below

To keep up to date follow us on the below channels.