# CVE-2022-24851: Stored XSS and path traversal in LDAPAccountManager/lam

> Authenticated attackers can inject stored XSS payloads or traverse paths in LDAP Account Manager, potentially executing code or reading files when profiles are accessed.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Apr 2022
- **Updated:** 22 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-24851, GHSA-f2fr-cccr-583v, UBUNTU-CVE-2022-24851

## What is CVE-2022-24851?

CVE-2022-24851 is a high-severity cross-site scripting vulnerability in Debian Debian Linux, published on 15 Apr 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

LDAP Account Manager (LAM) is an open source web frontend for managing entries stored in an LDAP directory. The profile editor tool has an edit profile functionality, the parameters on this page are not properly sanitized and hence leads to stored XSS attacks. An authenticated user can store XSS payloads in the profiles, which gets triggered when any other user try to access the edit profile page. The pdf editor tool has an edit pdf profile functionality, the logoFile parameter in it is not properly sanitized and an user can enter relative paths like ../../../../../../../../../../../../../usr/share/icons/hicolor/48x48/apps/gvim.png via tools like burpsuite. Later when a pdf is exported using the edited profile the pdf icon has the image on that path(if image is present). Both issues require an attacker to be able to login to LAM admin interface. The issue is fixed in version 7.9.1.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-24851?

It affects 2 products.


Products: Debian Debian Linux, Ldap-Account-Manager Ldap Account Manager.

## How do I fix CVE-2022-24851?

Upgrade to a fixed version.

## Is CVE-2022-24851 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24851 and fix it if it is affected.

What it is: CVE-2022-24851 is a high-severity cross-site scripting vulnerability in Debian Debian Linux, published on 15 Apr 2022. An attacker needs administrator access to exploit it, 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-2022-24851 exists.

Affected product: Debian Debian Linux. 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-2022-24851/ (Markdown: https://insights.sbomify.com/CVE-2022-24851/index.md)
```

## Sources

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

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