dbcve.org
InjectionWeakness · CWE-74

CVE-2025-13208

MEDIUM · 6.3 CVSS v3.1 Published 2025-11-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 security flaw has been discovered in FantasticLBP Hotels Server up to 67b44df162fab26df209bd5d5d542875fcbec1d0. The impacted element is an unknown function of the file controller/api/hotelList.php. The manipulation of the argument subjectId/cityName results in sql injection. The attack can be executed remotely. The exploit has been released to the public and may be exploited. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

SQL injection vulnerability in FantasticLBP Hotels Server's hotelList.php API endpoint. User-supplied parameters 'subjectId' and 'cityName' are directly incorporated into SQL queries without sanitization or parameterized queries, allowing remote attackers to inject arbitrary SQL code and potentially extract, modify, or delete database contents.

MitigationReplace direct string concatenation in SQL queries with prepared statements/parameterized queries. Apply input validation on all user-supplied parameters and ensure database accounts use least privilege.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checks

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

  1. Locate the hotelList.php file
    Search the web server document root for hotelList.php using: find /var/www -name 'hotelList.php' or dir /s C:\inetpub (Windows)
    Affected if The file exists in the environment, indicating the FantasticLBP Hotels Server component is installed
  2. Verify the vulnerable parameters are handled
    Open hotelList.php and search for 'subjectId' and 'cityName' in the code to confirm these parameters are processed by the endpoint
    Affected if The code reads and uses these parameters from GET or POST requests
  3. Inspect SQL query construction
    Examine the SQL queries in hotelList.php that incorporate subjectId and cityName - look for direct concatenation like $sql = "SELECT ... WHERE subjectId=" . $_REQUEST['subjectId']
    Affected if The parameters are concatenated directly into SQL queries without prepared statements, binding, or escaping functions
  4. Check for input validation or sanitization
    Search the hotelList.php code for sanitization functions (mysqli_real_escape_string, htmlspecialchars, preg_match validation) applied to subjectId and cityName before SQL use
    Affected if No input validation or sanitization functions are found applied to these parameters before they are used in SQL queries
  5. Confirm the endpoint is accessible
    Test if the hotelList.php endpoint responds by making a request to the URL (e.g., GET /api/hotelList.php?subjectId=1&cityName=test)
    Affected if The endpoint is reachable from the network, making the SQL injection exploitable remotely

If hotelList.php exists, handles subjectId/cityName parameters, and uses them in SQL queries without prepared statements or input sanitization, the environment is vulnerable to CVE-2025-13208.

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

Replace direct string concatenation in SQL queries with prepared statements/parameterized queries. Apply input validation on all user-supplied parameters and ensure database accounts use least privilege.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13208 — 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-13208 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