# CVE-2016-15048: AMTT HiBOS Command Injection RCE via server_ping.php

> Unauthenticated attackers can execute arbitrary system commands via the server_ping.php endpoint in AMTT HiBOS.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Oct 2025
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-9q3m-rvj5-q6fv

## What is CVE-2016-15048?

CVE-2016-15048 is a critical command injection vulnerability in Anmei Century (Beijing) Technology Co., Ltd. Hotel Broadband Operation System (HiBOS), published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AMTT Hotel Broadband Operation System (HiBOS) contains an unauthenticated command injection vulnerability in the /manager/radius/server_ping.php endpoint. The application constructs a shell command that includes the user-supplied ip parameter and executes it without proper validation or escaping. An attacker can insert shell metacharacters into the ip parameter to inject and execute arbitrary system commands as the web server user. The initial third-party disclosure in 2016 recommended contacting the vendor for remediation guidance. Additionally, this product may have been rebranded under a different name. VulnCheck has observed this vulnerability being exploited in the wild as of 2025-10-14 at 04:45:53.510819 UTC.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2016-15048?

It affects 1 product.


Products: Amttgroup Hibos.

## How do I fix CVE-2016-15048?

No fix has been published for CVE-2016-15048 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-15048 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-15048 exists.

## Other vulnerabilities in Anmei Century (Beijing) Technology Co., Ltd. Hotel Broadband Operation System (HiBOS)

- [CVE-2024-41476](https://insights.sbomify.com/CVE-2024-41476/): SQL injection in n/a (critical 9.8)
- [CVE-2023-6647](https://insights.sbomify.com/CVE-2023-6647/): AMTT HiBOS sql injection (high 7.3)
- [CVE-2025-12253](https://insights.sbomify.com/CVE-2025-12253/): AMTT Hotel Broadband Operation System get_expiredtime.php sql injection (medium 6.9)
- [CVE-2024-39072](https://insights.sbomify.com/CVE-2024-39072/): SQL injection in n/a (medium 5.5)
- [CVE-2025-13123](https://insights.sbomify.com/CVE-2025-13123/): AMTT Hotel Broadband Operation System get_firstdate.php sql injection (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-15048 and fix it if it is affected.

What it is: CVE-2016-15048 is a critical command injection vulnerability in Anmei Century (Beijing) Technology Co., Ltd. Hotel Broadband Operation System (HiBOS), published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-15048 exists.

Affected product: Anmei Century (Beijing) Technology Co., Ltd. Hotel Broadband Operation System (HiBOS). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-15048/ (Markdown: https://insights.sbomify.com/CVE-2016-15048/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-15048
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-15048
- OSV: https://osv.dev/vulnerability/CVE-2016-15048

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-15048/
Summaries are generated and may contain mistakes; the official description above is the record.