Custom Tables
Affected versions: ≥ 1.0 and < 3.7.8
Full advisory: our disclosure post
Custom Tables versions 1.0 to 3.7.7 let an unauthenticated visitor upload a file with an attacker-chosen extension through any public Custom Tables submission form that has a file field. The file is a polyglot that passes the MIME check, it is written to a web-accessible tmp directory, and its stored path is returned in the response. By default it is served as static content, so attackers can host phishing or malware pages on your domain. Update Custom Tables to 3.7.8 or later, which also fixes an authenticated arbitrary file deletion through the file field. Until you can update, unpublish or restrict any menu item or module that shows a public Custom Tables add or edit form, and check the site tmp folder for files you did not put there.
The base metrics as Joomla CNA published them, and what each one means for a site running an affected version. Threat and environmental metrics are left out: they describe a moment or a particular install rather than the flaw.
9.5 Critical
CVSS 4.0, scored by Joomla CNACVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HCustom Tables
Affected versions: ≥ 1.0 and < 3.7.8
Full advisory: our disclosure post
Updating for CVE-2026-105606 alone can leave a site on a release another rule still matches. These are the other flaws we check for in the same extension.
Latest safe version: 3.7.8
A free audit tells you which of your Joomla and WordPress sites run an affected version, which are out of date, and which have not been backed up. No card required. If a site is already compromised, fix.mysites.guru is a single fixed fee per incident, usually resolved the same day.
This check is part of the mySites.guru Joomla vulnerability scanner, which reads every installed extension's version on each audit. Browse the rest of the Joomla vulnerability database.
Rules current as of 3 November 2026.