CVE-2026-7697
SQL Injection in AMTT Hotel Broadband Operation System
Publication date: 2026-05-03
Last updated on: 2026-05-05
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| anmei_century | hotel_broadband_operation_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-7697 is an SQL injection vulnerability in the Anmei Digital Hotel Broadband Operation System, specifically in the file /manager/card/cardhand_submit.php.
The vulnerability occurs because the 'id' parameter is directly used in a SQL query without proper sanitization, allowing an attacker to manipulate the SQL statement.
Exploitation requires access to the backend login interface, typically with default credentials (username: administrator, password: admin).
An attacker can inject crafted SQL payloads to retrieve sensitive information such as the current database name.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute unauthorized SQL queries on the backend database.
Potential impacts include unauthorized access to sensitive data, data manipulation, and compromise of the integrity and confidentiality of the system.
Since exploitation requires backend login access, the risk is higher if default or weak credentials are used.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the `/manager/card/cardhand_submit.php` endpoint for SQL injection via the `id` parameter. An attacker can attempt to inject SQL payloads into this parameter to see if the system is vulnerable.
A proof-of-concept involves injecting crafted SQL payloads into the `id` parameter to retrieve database information such as the current database name.
Detection commands can include using tools like curl or sqlmap to test the injection point. For example:
- Using curl to test for SQL injection: curl -X POST 'http://target/manager/card/cardhand_submit.php' -d 'id=1' and then with a payload like 'id=1 OR 1=1--'
- Using sqlmap to automate detection: sqlmap -u 'http://target/manager/card/cardhand_submit.php?id=1' --risk=3 --level=5
Note that the exploit requires access to the backend login interface, which by default uses credentials username: administrator and password: admin, so testing may require authentication.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the backend login interface to prevent unauthorized access, especially since default credentials (administrator/admin) are known.
Change default credentials immediately to strong, unique passwords to prevent attackers from exploiting the vulnerability.
Implement input validation and sanitization on the `id` parameter in `/manager/card/cardhand_submit.php` to prevent SQL injection.
If possible, apply any available patches or updates from the vendor. However, the vendor did not respond to the disclosure, so consider additional protective measures such as web application firewalls (WAF) to block malicious payloads.
Monitor logs for suspicious activity targeting the vulnerable endpoint.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The CVE-2026-7697 vulnerability is an SQL injection flaw that allows unauthorized access or manipulation of data in the affected system. Such unauthorized data access or manipulation can lead to breaches of sensitive information, which may impact compliance with data protection standards and regulations like GDPR and HIPAA.
Specifically, if personal or protected health information is stored or processed by the affected system, exploitation of this vulnerability could result in unauthorized disclosure or alteration of that data, violating confidentiality and integrity requirements mandated by these regulations.
However, the provided information does not explicitly state the presence of regulated data or direct compliance impacts.