# CVE-2026-1969: ThemeREX Addons < 2.38.5 - Unauthenticated Arbitrary File Upload

> Unauthenticated attackers can upload arbitrary files via an AJAX action, potentially leading to remote code execution on WordPress sites using ThemeREX Addons.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-qxq6-27j9-fv97

## What is CVE-2026-1969?

CVE-2026-1969 is a medium-severity vulnerability in Unknown trx_addons, published on 23 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The trx_addons WordPress plugin before 2.38.5 does not correctly validate file types in one of its AJAX action, allowing unauthenticated users to upload arbitrary file. This is due to an incorrect fix of CVE-2024-13448

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-1969 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1969 is a medium-severity vulnerability in Unknown trx_addons, published on 23 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1969 in the wild and no public exploit code.

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

## Sources

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

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