# CVE-2026-114358: SQL Injection Vulnerability in Radius Xenia M2M Platform


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-cgx5-hf2m-237r

## What is CVE-2026-114358?

CVE-2026-114358 is a critical vulnerability in Radius Xenia M2M Platform, published on 29 Oct 2026. 

### Official description

This
vulnerability exists in the Radius
Xenia M2M Platform due to insufficient validation of user supplied input in
the password recovery functionality in the web management interface. An
unauthenticated remote attacker could exploit this vulnerability by supplying
crafted SQL query through input fields to the targeted system. 

Successful exploitation of this vulnerability
could allow the attacker to gain unauthorized access to sensitive information,
enumerate database structure or modify database records on the targeted system.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-114358?


## How do I fix CVE-2026-114358?

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

## Is CVE-2026-114358 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114358 and fix it if it is affected.

What it is: CVE-2026-114358 is a critical vulnerability in Radius Xenia M2M Platform, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114358 in the wild and no public exploit code.

Affected product: Radius Xenia M2M Platform. 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-2026-114358/ (Markdown: https://insights.sbomify.com/CVE-2026-114358/index.md)
```

## Sources

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

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