Tournamatch < 4.7.1 - Subscriber+ Arbitrary File Deletion
- Exploited
- No known exploitation
- Fix
- Fixed in 4.7.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.7.1.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.15% · 4th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Tournamatch, a WordPress plugin, is affected by a flaw that lets a logged-in user with the Subscriber role or higher delete arbitrary files on the server, such as wp-config.php, which could lead to full control of the site. The attacker must be logged in with at least a Subscriber account, and the flaw is triggered when a new profile or team image is uploaded.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.6/10CVSS 9.6
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.7.1.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
- Posted on X by cve.now
Affected versions
- Unknown Tournamatch
fixed in 4.7.1
Evidence 1
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121379
Is CVE-2026-121379 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-121379?
Tournamatch: before 4.7.1.Source: cve.now feed data
How do I fix CVE-2026-121379?
Upgrade to a fixed version: 4.7.1.Source: cve.now feed data