Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessFind Joomla site with public Custom Tables form
-
ExploitSubmit polyglot file with controlled extension
-
ExecutionServer writes file to web-accessible tmp dir
-
ImpactRetrieve disclosed path, host malicious content under victim domain
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK
2 techniques across 2 tactics: Command and Control, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The target Joomla site must have the Custom Tables extension (version below 3.7.8) installed AND must expose a PUBLIC, unauthenticated Custom Tables submission form; against such sites the attacker uploads a polyglot file with an attacker-controlled extension to the web-accessible tmp directory, and the response discloses the stored path. The key limiting factor is the public submission form - installs without a publicly reachable form are not exploitable through this path. A second scoping factor: the file is served as static content by default, so the impact is hosting attacker-controlled content rather than code execution, unless the server is additionally configured to execute files (e.g. PHP) from the tmp directory, which is not the default. |
| Impact | The signals conflict and must be weighed carefully. The supplied CVSS 4.0 base score of 9.5 is driven by all three vulnerable-system impacts and all three subsequent-system impacts being rated High (VC:H/VI:H/VA:H/SC:H/SI:H/SA:H), which implies full compromise. The description does not support that: it states the uploaded file is 'served as static content' by default, so the realistic primary impact is an unauthenticated arbitrary file WRITE to a web-accessible directory (integrity), not code execution or data destruction - confidentiality and availability impact appear minimal, so the headline 9.5 looks inflated relative to the described mechanism. Working in the attacker's favor: AV:N, AC:L, PR:N and UI:N mean this is reachable by remote unauthenticated attackers with no user interaction, and the vuln.today Decision label is act_now, so it should be prioritized. Working against widespread mass exploitation: AT:P reflects a real precondition - the target must expose a PUBLIC Custom Tables submission form - so only a subset of installs are exploitable. No EPSS score, no CISA KEV listing, and no verified exploit code were provided, so there is no evidence of active exploitation; the act_now label rests on the ease and unauthenticated nature of the write rather than on observed attacks. Net: treat as a genuine priority for sites running Custom Tables with a public submission form, but understand the concrete impact is attacker-controlled-content hosting (phishing/malware under the victim's domain) rather than confirmed remote code execution. |
| Exploit ScenarioDerived | A remote unauthenticated attacker locates a Joomla site running a vulnerable Custom Tables extension that exposes a public submission form, then submits a polyglot file with an attacker-chosen extension. The server stores it in the web-accessible tmp directory and discloses the stored path in the response, letting the attacker serve phishing or malware pages from the victim's own domain. No public exploit code was identified in the provided data, and exploitation requires that a public submission form be present. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 02, 2026
Unauthenticated arbitrary file upload in the Joomla Custom Tables extension before 3.7.8 allows an attacker to place a polyglot file with an attacker-controlled extension in the site's web-accessible tmp directory when a public Custom Tables submission form is exposed, and the response discloses the stored path. Because uploaded files are served as static content by default, the assessed impact is integrity only: hosting attacker-controlled content such as phishing or malware pages under the victim domain, not confirmed code execution. No public exploit was identified in the supplied data, and the supplied priority label is act_now.
RemediationAI
Upgrade the Custom Tables extension to version 3.7.8 or later (vendor-released patch: 3.7.8) and verify the update through the Joomla extension manager; the vendor reference is https://joomlaboat.com. If immediate upgrade is not possible, remove or restrict public Custom Tables submission forms, because the assessment identifies a publicly reachable form as the prerequisite for exploitation; the trade-off is that legitimate public submissions will be blocked. Ensure files in the tmp directory remain served as static content and are not configured for execution, which is consistent with the default behavior described in the assessment but does not replace upgrading.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-434, unrestricted upload of a file with a dangerous type, in the Custom Tables extension for Joomla. The supplied CPE is cpe:2.3:a:joomlaboat.com:custom_tables_extension_for_joomla:*:*:*:*:*:*:*:*, and the affected branch is Custom Tables before 3.7.8. The upload path targets the web-accessible tmp directory, accepts a polyglot file with an attacker-controlled extension, and returns the stored path in the response. The independent assessment assigns CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, so unauthenticated network exploitation is scoped to integrity impact; confidentiality and availability are not assessed as impacted. Default static serving of the tmp directory limits the outcome to hosting attacker-controlled content, while execution from that directory would require a non-default configuration and is not confirmed by the supplied evidence. The provided CVSS 4.0 vector includes attack requirements (AT:P) and broad scope metrics, but the authoritative assessment treats the public submission form as the key prerequisite.
Know when Custom Tables Extension For Joomla gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Remote unauthenticated write with no interaction (AV:N/AC:L/PR:N/UI:N); integrity-only (I:H) because files are served as static content, with no confidentiality or availability impact.
Primary rating from Vendor (Joomla).
CVSS VectorVendor: Joomla
DescriptionCVE.org
Joomla Extension - joomlaboat.com - Unauthenticated arbitrary file upload in Custom Tables < 3.7.8 - An unauthenticated attacker can upload a polyglot file with an attacker-controlled extension to the web-accessible tmp directory of any Joomla site that exposes a public Custom Tables submission form, and the stored path is disclosed in the response. By default the uploaded file is served as static content, so the primary impact is an unauthenticated arbitrary file write to a web-accessible directory, which allows hosting of attacker-controlled content (for example phishing or malware pages) under the victim's domain.
Executive ViewAI
A critical unauthenticated file upload vulnerability in the Joomla Custom Tables extension (versions before 3.7.8) allows attackers to host malicious files on the organization's website, potentially damaging brand trust and enabling phishing campaigns that target customers and partners. Leadership should prioritize remediation because this flaw can be exploited without authentication by anyone with access to a public submission form, and no official patch is currently available.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling public submission forms, restricting write access to the tmp directory, implementing file upload filtering via a WAF, and monitoring for anomalous file uploads.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
EUVD-2026-115367
NVD
CVE.org
Vulnrichment
GitHub PoC
Exploit-DB