# CVE-2024-48823: Path traversal in n/a

> A remote attacker can escalate privileges via local file inclusion in the PassageAutoServer.php page of Automatic Systems Maintenance devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2024
- **Updated:** 15 Mar 2025
- **Also known as:** GHSA-pqjf-jm5p-23mq

## What is CVE-2024-48823?

CVE-2024-48823 is a critical path traversal vulnerability in n/a, published on 14 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Local file inclusion in Automatic Systems Maintenance SlimLane 29565_d74ecce0c1081d50546db573a499941b10799fb7 allows a remote attacker to escalate privileges via the PassageAutoServer.php page.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2024-48823?


## How do I fix CVE-2024-48823?

No fix has been published for CVE-2024-48823 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-48823 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48823 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-48823 and fix it if it is affected.

What it is: CVE-2024-48823 is a critical path traversal vulnerability in n/a, published on 14 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48823 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-48823/ (Markdown: https://insights.sbomify.com/CVE-2024-48823/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-48823
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-48823
- OSV: https://osv.dev/vulnerability/CVE-2024-48823

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-48823/
Summaries are generated and may contain mistakes; the official description above is the record.