Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconAuthenticate to TinyFileManager instance
-
DeliveryInvoke Remote URL File Upload Module
-
ExploitSupply attacker-hosted malicious file URL
-
InstallBypass upload type restrictions
-
C2Store PHP payload in webroot
-
ExecuteRequest uploaded file to execute
-
ImpactGain code execution on server
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 attacker must have authenticated access to the target TinyFileManager instance (CVSS PR:L), reachable over the network, and the deployment must expose the Remote URL File Upload Module through which a remote attacker-controlled URL is fetched and stored without file-type/extension restriction. Full server compromise is further contingent on the uploaded file landing in a web-served, script-executable directory so a PHP payload can be invoked - this execution step is not explicitly confirmed in the sources and is the main limiting factor beyond the authentication requirement. Affected versions are TinyFileManager 2.0 through 2.6; no fixed version is identified because the vendor did not respond to the disclosure. |
| Impact | This is a moderate, authentication-gated risk rather than an emergency. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) shows network-reachable, low-complexity exploitation but requires low-level privileges (PR:L) - an attacker must already be an authenticated user of TinyFileManager, which substantially limits the unauthenticated internet-wide threat. The vendor-supplied vector rates all impacts Low (VC:L/VI:L/VA:L) for a 5.3 score, but that likely understates a CWE-434 unrestricted upload: placing an arbitrary file (including PHP) into a web-served directory commonly escalates to code execution, which is why my independent assessment rates impact higher - note this conflict between the published Low impacts and the real-world webshell potential. Exploit maturity is E:P (proof-of-concept), not active exploitation: there is no CISA KEV listing and no EPSS score in the input, so there is no signal of widespread or confirmed in-the-wild use. A public PoC reference exists (a Google Drive link) but it is not verified as working exploit code. The vuln.today priority is 'this_month', consistent with a real but non-urgent issue. The vendor was contacted and did not respond, so no official fix is confirmed - a meaningful aggravating factor for defenders. |
| Exploit ScenarioDerived | An authenticated low-privilege user of a TinyFileManager (≤2.6) instance abuses the Remote URL File Upload Module to make the application fetch and store an attacker-controlled file without restriction on type or extension. If that file is a PHP payload written to a web-accessible path, the attacker requests it to obtain a webshell and remote code execution. A public PoC reference exists but is not verified as working exploit code, so reliability is unconfirmed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 25, 2026
Unrestricted file upload in TinyFileManager 2.0 through 2.6 allows a user who is already authenticated to the file manager (CVSS PR:L) to store arbitrary files through the Remote URL File Upload Module in tinyfilemanager.php without file-type or extension enforcement, which can escalate to PHP code execution if the storage location is web-served and script-executable. The vendor was contacted about the disclosure and did not respond, so no fixed release has been identified; exploitation requires valid credentials plus a deployment that exposes the remote-URL upload path. A public PoC reference exists (a linked Google Drive artifact); it is not verified as working exploit code, and there is no CISA KEV confirmation of active exploitation - the priority signal is 'this_month' rather than an emergency, consistent with the authentication gate.
RemediationAI
No vendor-released patch was identified at time of analysis: the maintainer did not respond to the disclosure, and no fixed TinyFileManager version exists, so upgrading is not an option and administrators must compensate. The most direct control is to remove or disable the Remote URL File Upload functionality in tinyfilemanager.php (or block the corresponding request in a reverse proxy/WAF rule), accepting that users lose the remote-fetch upload convenience. Because the flaw is authenticated (PR:L), tighten access to the instance itself - place it behind an SSO/HTTP-auth gate or IP allowlist restricted to trusted operators and force strong credentials, at the cost of broader access for legitimate users. To break the escalation path, move the managed storage directory outside the web root or disable script execution there (for example by turning off the PHP handler for that directory in the web server configuration), accepting that any legitimate PHP hosting in that folder stops working. Additionally, monitor the storage directory for newly written .php or other executable files and alert on unexpected remote-URL fetches; reference material is at https://vuldb.com/vuln/426120. An update should be re-checked against the upstream TinyFileManager project before assuming a fix remains unavailable.
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
TinyFileManager is a single-file PHP web file manager (tinyfilemanager.php) commonly dropped into a web root to browse, upload, edit and delete files on the host. The flaw is an instance of CWE-434 (Unrestricted Upload of File with Dangerous Type) in the component described as the Remote URL File Upload Module: instead of uploading from the local filesystem, the user supplies a remote URL that the server fetches and writes into the managed storage, and that write path does not adequately restrict the resulting file name, extension or content type. Because the feature is a server-side fetch triggered over HTTP, the CVSS 4.0 vector rates the attack as network-reachable with low attack complexity and no attack requirements (AV:N/AC:L/AT:N); both the CVSS 4.0 vector (PR:L) and the authoritative CVSS 3.1 assessment (PR:L) indicate that valid credentials on the instance are a prerequisite, so this is not a pre-authentication flaw. The published score is 5.3, while the independent assessment is higher (CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, E:P) because a successful arbitrary write into a PHP-executable directory would give full control of the file manager's host - however, that final execution step depends on the upload directory being both web-served and configured to execute scripts, which is not confirmed in the available sources. The trigger mechanics beyond the URL-fetch upload path are not described in the available sources.
Know when Tinyfilemanager 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:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Authenticated (PR:L) remote, low-complexity upload of arbitrary files to the webroot typically yields a PHP webshell and full compromise, so C/I/A rated High.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A security vulnerability has been detected in prasathmani TinyFileManager up to 2.6. Affected by this issue is some unknown functionality of the file tinyfilemanager.php of the component Remote URL File Upload Module. The manipulation leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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.
More in Tinyfilemanager
View allPath traversal in prasathmani TinyFileManager up to version 2.6 allows authenticated remote attackers to manipulate the
Server-side request forgery (SSRF) in TinyFileManager file upload handler (versions up to 2.6) allows authenticated remo
EUVD-2026-109338
GHSA-6wpw-wr63-qhp5
NVD
CVE.org
EPSS
VulDB
Exploit-DB