CVE-2026-121379 Tournamatch < 4.7.1 - Subscriber+ Arbitrary File Deletion
Critical 9.6
Published
Updated
Check this codebase for CVE-2026-121379 and fix it if it is affected.
What it is: CVE-2026-121379 is a critical vulnerability in Tournamatch, published on 7 Nov 2026.
Exploitation: There is no known exploitation of CVE-2026-121379 in the wild and no public exploit code.
Affected product: Tournamatch. 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-121379/ (Markdown: https://insights.sbomify.com/CVE-2026-121379/index.md)
- Exploited in the wild
- Not known
- Fix
- 4.7.1
What is CVE-2026-121379?
CVE-2026-121379 is a critical vulnerability in Tournamatch, published on 7 Nov 2026.
Official description
The Tournamatch WordPress plugin before 4.7.1 does not validate or restrict the path of a previously stored profile or team image before deleting it when a new image is uploaded, allowing users with a role as low as Subscriber to delete arbitrary files on the server, such as wp-config.php, which can lead to a full site takeover.
Weakness: CWE-73
Which versions are affected by CVE-2026-121379?
How do I fix CVE-2026-121379?
Upgrade Tournamatch to 4.7.1 or later. The advisory says that version fixes it.
Is CVE-2026-121379 being exploited?
There is no known exploitation of CVE-2026-121379 in the wild and no public exploit code.
Sources
Also known as GHSA-6hvc-jpr4-hmmg.