CVE-2025-14710
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 · uneditedA vulnerability was detected in FantasticLBP Hotels Server up to 67b44df162fab26df209bd5d5d542875fcbec1d0. This affects an unknown part of the file /controller/api/OrderList.php. The manipulation of the argument telephone results in sql injection. The attack can be executed remotely. The exploit is now public and may be used. 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 confidenceSQL injection vulnerability in FantasticLBP Hotels Server's /controller/api/OrderList.php API endpoint. The telephone parameter is not properly sanitized, allowing attackers to inject malicious SQL queries. This can lead to unauthorized database access, data exfiltration, or potential remote code execution depending on database configuration.
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<= 2019-03-23CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 FantasticLBP Hotels Server installationSearch the server filesystem for the 'Fantasticlbp' or 'Hotels' directory structure, typically under the web root (e.g., /var/www/html, /htdocs, or C:\inetpub\wwwroot). Look for the OrderList.php file in the /controller/api/ directory.Affected if The application is installed and the OrderList.php file exists in the /controller/api/ path.
-
Determine installed versionExamine version files, changelogs, or metadata within the installation directory. Check for files like version.txt, README, or the main entry point that displays version information. Compare against the affected version: <= 2019-03-23Affected if The installed version is dated 2019-03-23 or earlier.
-
Verify the vulnerable endpoint existsConfirm the file /controller/api/OrderList.php is present on the server. Check the file contents for code that handles the 'telephone' parameter in SQL queries without prepared statements.Affected if The OrderList.php file exists and contains SQL queries using the telephone parameter directly.
-
Inspect telephone parameter handlingReview the OrderList.php source code. Search for SQL query construction involving 'telephone' or $_GET/$_POST['telephone']. Look for lack of parameterized queries, prepared statements, or input sanitization functions.Affected if The telephone parameter is used in SQL queries without prepared statements, parameter binding, or evident sanitization.
-
Check web server access logsReview web server access logs (Apache access.log, Nginx access.log) for requests to /controller/api/OrderList.php with a telephone parameter. Look for anomalous SQL syntax or unexpected characters in the parameter values.Affected if Requests to the endpoint contain SQL injection payloads or unusual characters in the telephone parameter.
A user is affected if FantasticLBP Hotels Server version 2019-03-23 or earlier is installed and the /controller/api/OrderList.php endpoint processes the telephone parameter in SQL queries without prepared statements.
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 parameterized queries (prepared statements) for all database operations involving user input, specifically the telephone parameter. Apply input validation and output encoding as defense-in-depth measures.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14710 — 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-14710 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