Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14090: SQL Injection in AMTT Hotel Broadband Operation System

0
Medium
VulnerabilityCVE-2025-14090cvecve-2025-14090
Published: Fri Dec 05 2025 (12/05/2025, 15:32:08 UTC)
Source: CVE Database V5
Vendor/Project: AMTT
Product: Hotel Broadband Operation System

Description

A security flaw has been discovered in AMTT Hotel Broadband Operation System 1.0. This affects an unknown part of the file /manager/card/cardmake_down.php. Performing manipulation of the argument ID results in sql injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

AILast updated: 12/05/2025, 16:00:52 UTC

Technical Analysis

CVE-2025-14090 is a SQL injection vulnerability identified in version 1.0 of the AMTT Hotel Broadband Operation System, specifically within the /manager/card/cardmake_down.php script. The vulnerability arises from improper sanitization of the 'ID' parameter, allowing an attacker to inject malicious SQL commands remotely without requiring authentication or user interaction. This flaw can be exploited to manipulate backend database queries, potentially leading to unauthorized data access, modification, or disruption of service. The vulnerability has a CVSS 4.0 score of 5.1, reflecting medium severity with network attack vector, low complexity, no privileges required, and no user interaction. The vendor was notified but has not responded or provided a patch, and public exploit code is available, increasing the risk of exploitation. The vulnerability impacts confidentiality, integrity, and availability at a limited level, as the scope is confined to the affected system and the specific parameter. The lack of authentication requirement and remote exploitability make this a notable risk for organizations using this system, particularly in the hospitality sector where AMTT's broadband management solutions are deployed. The vulnerability's exploitation could lead to data leakage, unauthorized administrative actions, or service interruptions, affecting hotel operations and guest services.

Potential Impact

For European organizations, particularly those in the hospitality and tourism sectors relying on AMTT Hotel Broadband Operation System 1.0, this vulnerability poses a tangible risk of unauthorized data access and potential service disruption. Exploitation could compromise guest data confidentiality, including personal and payment information, damaging organizational reputation and leading to regulatory penalties under GDPR. Integrity of operational data could be affected, potentially disrupting billing or network access controls, impacting guest experience and operational continuity. Availability may be degraded if attackers manipulate database queries to cause system errors or downtime. Given the public availability of exploit code and lack of vendor patch, the risk of targeted attacks or opportunistic exploitation is elevated. European hotels with limited cybersecurity resources may be particularly vulnerable, and the impact could extend to supply chain partners relying on the broadband system. The medium severity rating suggests that while the vulnerability is not critical, it requires prompt attention to avoid escalating risks.

Mitigation Recommendations

Since no official patch is available from the vendor, European organizations should implement immediate compensating controls. These include deploying web application firewalls (WAFs) with rules to detect and block SQL injection attempts targeting the 'ID' parameter in /manager/card/cardmake_down.php. Network segmentation should isolate the affected system from broader corporate networks to limit lateral movement. Input validation and parameter sanitization should be enforced at the application or proxy level if possible. Regular monitoring of logs for suspicious database queries or repeated access attempts to the vulnerable endpoint is essential. Organizations should also consider disabling or restricting access to the vulnerable functionality if feasible. Incident response plans should be updated to address potential exploitation scenarios. Long-term mitigation requires vendor engagement for patch development or migration to alternative solutions. Additionally, conducting security audits and penetration testing focused on web application vulnerabilities can help identify and remediate similar issues proactively.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-12-05T08:48:41.294Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6932fe10f88dbe026cf26f4f

Added to database: 12/5/2025, 3:45:20 PM

Last enriched: 12/5/2025, 4:00:52 PM

Last updated: 12/6/2025, 3:54:37 AM

Views: 9

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats