# CVE-2024-48821: Cross-site scripting in n/a

> A remote attacker can escalate privileges via a Cross Site Scripting vulnerability in the FtpConfig.php component of Automatic Systems Maintenance.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Oct 2024
- **Updated:** 24 Mar 2025
- **Also known as:** GHSA-8f5f-8xpp-8qfr

## What is CVE-2024-48821?

CVE-2024-48821 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross Site Scripting vulnerability in Automatic Systems Maintenance SlimLane 29565_d74ecce0c1081d50546db573a499941b10799fb7 allows a remote attacker to escalate privileges via the FtpConfig.php component.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2024-48821 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48821 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48821 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-48821/ (Markdown: https://insights.sbomify.com/CVE-2024-48821/index.md)
```

## Sources

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

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