# CVE-2018-25144: Microhard Systems IPn4G 1.1.0 Arbitrary File Access via Undocumented System Editor

> Authenticated attackers can read, modify, or delete arbitrary files on Microhard Systems IPn4G gateways via unsanitized parameters in the hidden system editor.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Dec 2025
- **Updated:** 2 Feb 2026
- **Also known as:** GHSA-gpch-6qpg-rp8g

## What is CVE-2018-25144?

CVE-2018-25144 is a high-severity path traversal vulnerability in Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Arbitrary File Attacks, published on 24 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Microhard Systems IPn4G 1.1.0 contains an authentication bypass vulnerability in the hidden system-editor.sh script that allows authenticated attackers to read, modify, or delete arbitrary files. Attackers can exploit unsanitized 'path', 'savefile', 'edit', and 'delfile' parameters to perform unauthorized file system modifications through GET and POST requests.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2018-25144?

It affects 11 products.


Products: Microhardcorp Bullet-3g Firmware, Microhardcorp Bullet-Lte Firmware, Microhardcorp Bulletplus Firmware, Microhardcorp Dragon-Lte Firmware, Microhardcorp Ipn3gb Firmware, Microhardcorp Ipn3gii Firmware, Microhardcorp Ipn4g Firmware, Microhardcorp Ipn4gb Firmware, Microhardcorp Ipn4gii Firmware, Microhardcorp Vip4gb Firmware, Microhardcorp Vip4gb Wifi-N Firmware.

## How do I fix CVE-2018-25144?

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

## Is CVE-2018-25144 being exploited?

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

## Other vulnerabilities in Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Arbitrary File Attacks

- [CVE-2018-25147](https://insights.sbomify.com/CVE-2018-25147/): Microhard Systems IPn4G 1.1.0 Default Credentials Authentication Bypass (critical 9.3)
- [CVE-2018-25143](https://insights.sbomify.com/CVE-2018-25143/): Microhard Systems IPn4G 1.1.0 Backdoor Jailbreak via Microhard Sh Service (high 8.7)
- [CVE-2018-25148](https://insights.sbomify.com/CVE-2018-25148/): Microhard Systems IPn4G 1.1.0 Remote Code Execution via Admin Interface (high 8.7)
- [CVE-2018-25145](https://insights.sbomify.com/CVE-2018-25145/): Microhard Systems IPn4G 1.1.0 Configuration Disclosure via Authenticated Download (high 7.1)
- [CVE-2018-25146](https://insights.sbomify.com/CVE-2018-25146/): Microhard Systems IPn4G 1.1.0 Service Control Denial of Service (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25144 and fix it if it is affected.

What it is: CVE-2018-25144 is a high-severity path traversal vulnerability in Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Arbitrary File Attacks, published on 24 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25144 exists.

Affected product: Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Arbitrary File Attacks. 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-2018-25144/ (Markdown: https://insights.sbomify.com/CVE-2018-25144/index.md)
```

## Sources

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

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