CVE-2025-14090VulnerabilityPublished 5 Dec 2025

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

Affects AMTT Hotel Broadband Operation SystemSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
AMTT Hotel Broadband Operation System	Affected =1.0	Fixed in–

AI-suggested

1. Implement strict input validation and parameterized queries in the affected application component to prevent SQL injection. 2. Restrict access to the /manager/card/cardmake_down.php endpoint using network segmentation and firewall rules, limiting it to trusted administrative networks only. 3. Enforce strong authentication and role-based access controls to minimize the number of users with high privileges. 4. Monitor logs and network traffic for unusual queries or access patterns indicative of SQL injection attempts. 5. Conduct regular security audits and penetration testing focused on web application vulnerabilities. 6. If possible, isolate the broadband operation system from other critical infrastructure to contain potential breaches. 7. Engage with the vendor for patch development or consider alternative solutions if remediation is delayed. 8. Educate internal staff about the risks of privilege misuse and enforce strict credential management policies.

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.

Impact

For European organizations, particularly those in the hospitality sector using AMTT Hotel Broadband Operation System 1.0, this vulnerability poses a risk to the confidentiality and integrity of customer and operational data. Attackers with high privileges could exploit the SQL injection to extract sensitive information, alter broadband access controls, or disrupt network services, leading to service outages or data breaches. This could result in reputational damage, regulatory penalties under GDPR for data exposure, and operational downtime. The impact is heightened in large hotel chains or resorts where broadband access management is critical for guest services. Additionally, compromised broadband systems could serve as pivot points for further network intrusion. The lack of vendor patches increases exposure duration, necessitating proactive defensive measures. While the vulnerability requires high privileges, insider threats or compromised credentials could facilitate exploitation, making internal security controls vital.

Summary

CVE-2025-14090 identifies a SQL injection vulnerability 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, which an attacker can manipulate to inject arbitrary SQL commands. This flaw allows remote exploitation without user interaction but requires high privileges, indicating that an attacker must already have some level of authenticated access to the system. The injection can lead to unauthorized data access, modification, or deletion, impacting the confidentiality, integrity, and availability of the backend database. The vendor was notified early but has not issued any patches or advisories, and no known exploits are currently active in the wild. The CVSS 4.0 vector indicates network attack vector, low complexity, no user interaction, and no privileges required for attack execution, but the presence of 'PR:H' (privileges required: high) suggests that exploitation is limited to users with elevated access. The vulnerability affects a critical component managing broadband access cards in hotel environments, potentially allowing attackers to manipulate user access or disrupt service. Given the public disclosure and lack of vendor response, the risk of exploitation may increase over time.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Dec 2025, 16:32 UTC

Technical details

References

Community reviews

Related threats