# CVE-2025-10183: XML External Entity Injection in TecConnect 4.1

> An unauthenticated attacker can exploit blind XXE in TecConnect to exfiltrate arbitrary files to an external server.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2025
- **Updated:** 9 Sep 2025
- **Also known as:** GHSA-96j8-8455-q77x

## What is CVE-2025-10183?

CVE-2025-10183 is a critical vulnerability in TecCom TecConnect, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A blind XML External Entity (XXE) injection in the OpenMessaging webservice in TecCom TecConnect 4.1 allows an unauthenticated attacker to exfiltrate arbitrary files to an attacker-controlled server. TecConnect 4.1 is considered end-of-life as of December 2023. Users are advised to upgrade to TecCom Connect 5.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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


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

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

## Is CVE-2025-10183 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10183 is a critical vulnerability in TecCom TecConnect, published on 9 Sep 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-2025-10183 exists.

Affected product: TecCom TecConnect. 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-10183/ (Markdown: https://insights.sbomify.com/CVE-2025-10183/index.md)
```

## Sources

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

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