# CVE-2026-54223: Remote Code Execution via arbitrary file read and write in UBB.threads

> Privileged attackers can exploit path traversal in UBB.threads to read/write arbitrary files, leading to remote code execution.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jun 2026
- **Updated:** 18 Jun 2026
- **Also known as:** GHSA-jgf8-gg7j-fq24

## What is CVE-2026-54223?

CVE-2026-54223 is a high-severity path traversal vulnerability in UBB.threads, published on 18 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

UBB.threads is vulnerable to Path traversal, allowing attackers with privilege to edit templates to read and write any file on the application’s server that application has privileges to, what results in Remote Code Execution. 
Because vendor contact attempts were unsuccessful, the vulnerability has only been confirmed in version 7.7.5 but may also affect other versions.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-54223 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54223 is a high-severity path traversal vulnerability in UBB.threads, published on 18 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54223 in the wild and no public exploit code.

Affected product: UBB.threads. 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-54223/ (Markdown: https://insights.sbomify.com/CVE-2026-54223/index.md)
```

## Sources

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

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