The Tournamatch WordPress plugin before 4.7.1 does not validate or restrict the path of a previously stored profile or
Source GCVE Database
Not known to be exploited : upgrade to 4.7.1 soon.
Data as of 7 Nov 2026, 07:37 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 4.7.1
Exploitation evidence
Disclosed: evidence found.
CVE published 7 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade Tournamatch (WordPress plugin) to 4.7.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Tournamatch | Affected
| Fixed in
|
AI-suggested
Upgrade the Tournamatch WordPress plugin to version 4.7.1 or later where this vulnerability is fixed. No other mitigation is indicated since the fix is available in the updated plugin version.
Description
The Tournamatch WordPress plugin versions prior to 4.7.1 contain a vulnerability where the plugin does not validate or restrict the path of a previously stored profile or team image before deleting it during a new image upload. This flaw allows users with minimal privileges, such as Subscribers, to delete arbitrary files on the server, including critical files like wp-config.php, potentially leading to a full site takeover.