CVE-2026-127142: LMS: unrestricted file upload enables authenticated RCE
AWAITING NVDLMS (Lan Management System) has an unrestricted file upload flaw (CWE-434) in the service ticket feature of its client panel. An authenticated user can upload an .htaccess file to bypass the storage directory's access restrictions, then upload a PHP script and request its URL to run arbitrary code as the web server user. LMS is an ISP and network management application, not an AI/ML product, so the AI classification (ml_ui) looks like a mislabel and the link to AI risk is indirect. There is no CVSS or EPSS score, no CISA KEV listing, no public exploit and no Nuclei template, so there is no sign of active exploitation yet. The exploit is simple, though, and any customer account is enough to launch it. The fix is in upstream commit 89dd3f7 (chilek/lms), so patch to a build that includes it, and meanwhile block script execution in the upload directory and review the CERT.PL advisory.
What is the risk?
Severity is not yet scored. Based on the description, impact would be high: arbitrary code execution as the web server user. Exploitation is trivial but needs an authenticated client-panel account, and those accounts are often issued to many customers. EPSS is unavailable, there is no KEV listing and no public exploit, so exploitation likelihood is currently unquantified. Exposure is highest for internet-facing client panels. The AI/ML relevance is low: no AI package from our tracked catalog is affected, and the ml_ui category is probably a misclassification.
How does the attack unfold?
How severe is it?
What should I do?
1 step1) Update LMS to a version or commit that includes 89dd3f75168a99f1a0a3539957d08715bb86ab4f. 2) Until patched, disable script execution (PHP handler) in the storage and upload directories at the web server level, and set AllowOverride None so .htaccess files in uploads are ignored. 3) Restrict or temporarily disable file attachments in the client panel ticket feature. 4) Detection: search the storage directories for .htaccess, .php, .phtml or other executable files, and review web logs for requests to those files and for unusual child processes spawned by the web server user. 5) Audit client accounts for suspicious signups and rotate credentials if compromise is suspected. 6) Run the web server with least privilege and isolate it from sensitive internal and ML systems.
How is it classified?
Which compliance frameworks are affected?
Compliance analysis pending. Sign in for full compliance mapping when available.
Frequently Asked Questions
What is CVE-2026-127142?
LMS (Lan Management System) has an unrestricted file upload flaw (CWE-434) in the service ticket feature of its client panel. An authenticated user can upload an .htaccess file to bypass the storage directory's access restrictions, then upload a PHP script and request its URL to run arbitrary code as the web server user. LMS is an ISP and network management application, not an AI/ML product, so the AI classification (ml_ui) looks like a mislabel and the link to AI risk is indirect. There is no CVSS or EPSS score, no CISA KEV listing, no public exploit and no Nuclei template, so there is no sign of active exploitation yet. The exploit is simple, though, and any customer account is enough to launch it. The fix is in upstream commit 89dd3f7 (chilek/lms), so patch to a build that includes it, and meanwhile block script execution in the upload directory and review the CERT.PL advisory.
Is CVE-2026-127142 actively exploited?
No confirmed active exploitation of CVE-2026-127142 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-127142?
1) Update LMS to a version or commit that includes 89dd3f75168a99f1a0a3539957d08715bb86ab4f. 2) Until patched, disable script execution (PHP handler) in the storage and upload directories at the web server level, and set AllowOverride None so .htaccess files in uploads are ignored. 3) Restrict or temporarily disable file attachments in the client panel ticket feature. 4) Detection: search the storage directories for .htaccess, .php, .phtml or other executable files, and review web logs for requests to those files and for unusual child processes spawned by the web server user. 5) Audit client accounts for suspicious signups and rotate credentials if compromise is suspected. 6) Run the web server with least privilege and isolate it from sensitive internal and ML systems.
What systems are affected by CVE-2026-127142?
This vulnerability affects the following AI/ML architecture patterns: Web-based management applications, Customer self-service portals.
What is the CVSS score for CVE-2026-127142?
No CVSS score has been assigned yet.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0049Exploit Public-Facing ApplicationAML.T0050Command and Scripting InterpreterWhat are the technical details?
Original Advisory
LMS (Lan Management System) is vulnerable to Remote Code Execution via unrestricted upload of dangerous file types in the service ticket feature of the client panel. The application does not verify the type or name of files attached to service tickets. An authenticated attacker can upload an .htaccess file to bypass the access restrictions on the storage directory, together with a PHP script. Visiting the uploaded PHP file's URL leads to arbitrary code execution with the privileges of the web server. This issue was fixed in commit 89dd3f7.
Exploitation Scenario
An attacker registers or compromises a customer account on a public LMS client panel. They open a service ticket and attach an .htaccess file that re-enables script execution in the storage directory, then attach a PHP web shell. They browse to the shell's URL and run commands as the web server user. From there they dump the database and credentials and move laterally. If the host sits near ML infrastructure, they could reach internal model-serving or data stores.
Weaknesses (CWE)
CWE-434 — Unrestricted Upload of File with Dangerous Type: The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
- [Architecture and Design] Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.[REF-422] [REF-423]
- [Architecture and Design] When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Source: MITRE CWE corpus.
References
Timeline
Related Vulnerabilities
CVE-2024-291210.0BentoML: RCE via insecure deserialization (CVSS 10)
Same attack type: Code ExecutionCVE-2026-2185810.0n8n: Input Validation flaw enables exploitation
Same attack type: Code ExecutionCVE-2025-512010.0smolagents: sandbox escape enables unauthenticated RCE
Same attack type: Code ExecutionCVE-2025-5952810.0Flowise: Unauthenticated RCE via MCP config injection
Same attack type: Code ExecutionGHSA-vvpj-8cmc-gx3910.0picklescan: security flaw enables exploitation
Same attack type: Code Execution