# CVE-2025-9315: Unauthenticated Device Registration Vulnerability in MXsecurity Series

> Unauthenticated attackers can register unauthorized devices via a crafted JSON payload, allowing unauthorized access to the network device.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2025
- **Updated:** 10 Dec 2025
- **Also known as:** GHSA-8ggx-mv5h-wj7q

## What is CVE-2025-9315?

CVE-2025-9315 is a medium-severity authentication bypass vulnerability in Moxa MXsecurity Series, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated device registration vulnerability, caused by Improperly Controlled Modification of Dynamically-Determined Object Attributes, has been identified in the MXsecurity Series. An unauthenticated remote attacker can exploit this vulnerability by sending a specially crafted JSON payload to the device's registration endpoint /api/v1/devices/register, allowing the attacker to register unauthorized devices without authentication. Although exploiting this vulnerability has limited modification of data, there is no impact to the confidentiality and availability of the affected device, as well as no loss of confidentiality, integrity, and availability within any subsequent systems.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

## Which versions are affected by CVE-2025-9315?


## How do I fix CVE-2025-9315?

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

## Is CVE-2025-9315 being exploited?

There is no known exploitation of CVE-2025-9315 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9315 and fix it if it is affected.

What it is: CVE-2025-9315 is a medium-severity authentication bypass vulnerability in Moxa MXsecurity Series, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9315 in the wild and no public exploit code.

Affected product: Moxa MXsecurity Series. 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-2025-9315/ (Markdown: https://insights.sbomify.com/CVE-2025-9315/index.md)
```

## Sources

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

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