Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged tenant
-
DeliverySend upload with ../ in path parameter
-
ExploitWrite PHP webshell into other tenant web root
-
ExecutionRequest planted file over HTTP
-
PersistExecute code as victim tenant
-
ImpactCompromise cross-tenant site and data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid authenticated Laranode tenant account (PR:L) with access to the file manager upload feature, and a multi-tenant deployment where tenants share a host so that traversal into another tenant's home/web root is meaningful. The attacker supplies directory-traversal sequences in the path parameter of POST /filemanager/upload-file; pre-1.2.1 the endpoint concatenated user input directly ('/home/'+systemUsername+'/'+path) with no normalization or containment, so no special non-default configuration is needed beyond having the file manager enabled. Limiting factors: authentication is required (not unauthenticated), and full impact (code execution as another tenant) assumes the written PHP lands where the web server serves and interprets it; a single-tenant install limits the blast radius to the attacker's own account. |
| Impact | The vendor CVSS 4.0 base of 8.7 (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H) aligns well with the described mechanics: a network-reachable, low-complexity path traversal in the authenticated POST /filemanager/upload-file endpoint that lets any tenant write PHP into another tenant's web root and achieve code execution as that tenant. The PR:L (authenticated tenant) is the main gating factor - this is not an unauthenticated internet-wide bug, but any legitimate hosting-panel customer is a valid attacker, and in a shared multi-tenant panel the trust boundary between tenants is exactly what is broken. No EPSS score, CISA KEV entry, or public POC is present in the supplied data, so this is NOT confirmed to be under active exploitation; the intelligence here is a credible third-party report (VulnCheck) plus a confirmed vendor patch (PR #21 / commit 5c2b18ae / v1.2.1 release) rather than observed exploitation. Real-world priority is therefore driven by impact-per-exploit (cross-tenant RCE, trivially weaponized by planting a webshell) rather than by exploitation-in-the-wild evidence or by broad exposure - the product itself is niche. Note the vendor scored subsequent-system impact as SC:N/SI:N/SA:N even though the described outcome is compromise of OTHER tenants; that under-represents the cross-security-authority nature of the flaw versus a CVSS 3.1 scope-change reading. |
| Exploit ScenarioDerived | An attacker holds (or registers) a low-privileged tenant account on a shared Laranode host, then calls POST /filemanager/upload-file with directory-traversal sequences in the path parameter to escape their home directory and write a PHP webshell into a neighboring tenant's public web root. Requesting that planted file over HTTP executes attacker code in the victim tenant's context, fully compromising that tenant's site and data. No public POC is identified in the provided data, but the technique is trivial to reproduce from the confirmed patch diff. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 26, 2026
Authenticated path traversal in Laranode before 1.2.1 lets any tenant holding a valid account and file manager access write arbitrary files outside their own home directory via the POST /filemanager/upload-file endpoint, including dropping PHP files into other tenants' web roots for code execution as those tenants. The endpoint built its destination as '/home/' + systemUsername + '/' + user-supplied path with no normalization or containment, so a low-complexity traversal request is sufficient on multi-tenant hosts where the web server interprets the written PHP; vendor CVSS 4.0 rates this 8.7 (AV:N/AC:L/AT:N/PR:L/UI:N) and our independent CVSS 3.1 assessment (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) equally reflects cross-tenant scope change. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV entry); exploitation requires authentication, so single-tenant installations limit the blast radius to the attacker's own account.
RemediationAI
Upgrade Laranode to 1.2.1 or later - the vendor-released patch that normalizes the upload path, rejects non-basename filenames and invalid chunk indices, and routes all file manager writes through the descriptor-anchored SafeFileProcess helper; the release is available at https://github.com/crivion/laranode/releases/tag/v1.2.1, with the fix detailed in advisory https://github.com/crivion/laranode/security/advisories/GHSA-34h2-2696-vfvr, PR https://github.com/crivion/laranode/pull/21, and commit https://github.com/crivion/laranode/commit/5c2b18ae99caf77a6fb6cc5c0ab66562bd673424. Note that the patched Dockerfile and installer now require python3 as a hard runtime dependency and generate an explicit sudoers allowlist via laranode-scripts/bin/laranode-sudoers.sh, so custom images or manual VPS installs that bypass those steps will be broken or less protected after upgrade. If immediate upgrade is impossible, disable or block the file manager upload endpoint (or the file manager entirely) for non-administrative tenants - an effective containment with the trade-off of removing tenant file upload/management functionality - and avoid wildcard sudoers entries in favor of naming individual helper scripts. Restricting the deployment to single-tenant hosts reduces the blast radius so a successful traversal can only affect the attacker's own account rather than enabling code execution as another tenant, but it does not remove the traversal defect and should be treated only as a stopgap until 1.2.1 is applied.
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
Laranode is a PHP/Laravel hosting control panel that provisions per-tenant system users and home directories under /home/<systemUsername>, and the file manager is one of the panel's privileged write paths. The vulnerable code is app/Actions/Filemanager/UploadFileAction.php at tag v1.2, which validated 'path' only as 'required|string' and then concatenated it directly into '/home/' . $r->user()->systemUsername . '/' . $r->path before calling File::append, a classic CWE-22 path traversal with no canonicalization or root containment check. Because tenant web roots live alongside each other on the same host, '../' sequences in the path parameter both escape the caller's own directory and land writes in sibling tenants' document roots, where PHP files are served and executed by the tenant's web server. The v1.2.1 fix (PR #21, commit 5c2b18ae99caf77a6fb6cc5c0ab66562bd673424) introduces League\Flysystem\WhitespacePathNormalizer to normalize the relative path, rejects non-basename originalName values and out-of-range chunk indices, and funnels every mutation through a new App\Filesystem\SafeFileProcess helper that dispatches to a descriptor-anchored Python helper (app/Filesystem/safe_file.py) executed via a sudoers-allowlisted laranode-safe-file.sh script. That Dockerfile change also promotes python3 from an incidental certbot dependency to a hard runtime requirement and replaces a wildcard sudoers rule with an explicit per-script allowlist so a writable bin/ path cannot be turned into a root shell - hardening that is directly relevant to the same privileged-write threat model.
Know when Laranode 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:H/VI:H/VA:H/SC:N/SI:N/SA:N
Authenticated tenant (PR:L) writes executable code into another tenant's context, crossing a security-authority boundary (S:C) for full cross-tenant C/I/A impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Laranode versions before 1.2.1 contain a path traversal vulnerability in the POST /filemanager/upload-file endpoint that allows authenticated users to write arbitrary files outside their home directory. Attackers can supply directory traversal sequences in the path parameter to write PHP files into other tenants' web roots and execute code as those tenants.
Technical POC Analysis
CWE-22 (path traversal); the advisory also assigns CWE-59 for the link-following variant.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Latest POC
1 public PoC link from github
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
Laranode deployments before 1.2.1 expose multi-tenant hosting environments to cross-tenant file writes and potential code execution by an authenticated tenant with file manager access. This undermines tenant isolation on shared hosts, affecting other customers' web roots and data, and should concern leadership because it can lead to service compromise, customer data exposure, and reputational or contractual harm. The issue is rated high severity with no public exploit identified at time of analysis, and exploitation requires authentication.
Apply vendor patch.
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
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
EUVD-2026-87375
GHSA-7q7h-5g76-8cq4
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB