# CVE-2023-25356: Command injection in n/a

> XMPP users can inject arguments into system commands to read/write files and execute remote code on the sipXcom server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 4 Apr 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-36c8-4759-wcjr

## What is CVE-2023-25356?

CVE-2023-25356 is a high-severity command injection vulnerability in n/a, published on 4 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CoreDial sipXcom up to and including 21.04 is vulnerable to Improper Neutralization of Argument Delimiters in a Command. XMPP users are able to inject arbitrary arguments into a system command, which can be used to read files from, and write files to, the sipXcom server. This can also be leveraged to gain remote command execution.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2023-25356?

It affects 1 product.


Products: Coredial Sipxcom.

## How do I fix CVE-2023-25356?

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

## Is CVE-2023-25356 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-25355](https://insights.sbomify.com/CVE-2023-25355/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25356 and fix it if it is affected.

What it is: CVE-2023-25356 is a high-severity command injection vulnerability in n/a, published on 4 Apr 2023. 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-2023-25356 exists.

Affected product: n/a. 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-2023-25356/ (Markdown: https://insights.sbomify.com/CVE-2023-25356/index.md)
```

## Sources

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

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