# CVE-2022-4983: TEC-IT TBarCode SDK 11.15 Remote File Create

> Attackers can exploit the TBarCode SDK ActiveX control to create arbitrary files on the host, potentially leading to code execution or persistence.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Nov 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-p957-57wh-w9x8

## What is CVE-2022-4983?

CVE-2022-4983 is a medium-severity path traversal vulnerability in TEC-IT TBarCode, published on 12 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

TEC-IT TBarCode version 11.15 contains a vulnerability in the TBarCode11.ocx ActiveX/OCX control's licensing handling (INI-file based) that can be abused to cause remote creation of files on the host filesystem. Depending on where files can be created and which filenames are allowed, this can allow attackers to write files that lead to code execution or persistence under the context of the hosting process.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2022-4983?


## How do I fix CVE-2022-4983?

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

## Is CVE-2022-4983 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4983 and fix it if it is affected.

What it is: CVE-2022-4983 is a medium-severity path traversal vulnerability in TEC-IT TBarCode, published on 12 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-4983 in the wild and no public exploit code.

Affected product: TEC-IT TBarCode. 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-2022-4983/ (Markdown: https://insights.sbomify.com/CVE-2022-4983/index.md)
```

## Sources

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

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