# CVE-2018-20369: Cross-site scripting in n/a

> Cross-site scripting vulnerability in Barracuda Message Archiver allows attackers to inject malicious scripts via the ldap_user parameter.

- **Severity:** Medium 6.1 (`CVSS:3.0/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:** 23 Dec 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-p45m-hh26-3vgh

## What is CVE-2018-20369?

CVE-2018-20369 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Dec 2018. 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

Barracuda Message Archiver 2018 has XSS in the error_msg exception-handling value for the ldap_user parameter to the cgi-mod/ldap_load_entry.cgi module. The injection point of the issue is the Add_Update module.

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

## Which versions are affected by CVE-2018-20369?

It affects 1 product.


Products: Barracuda Message Archiver.

## How do I fix CVE-2018-20369?

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

## Is CVE-2018-20369 being exploited?

There is no known exploitation of CVE-2018-20369 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20369 and fix it if it is affected.

What it is: CVE-2018-20369 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Dec 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-20369 in the wild and no public exploit code.

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-2018-20369/ (Markdown: https://insights.sbomify.com/CVE-2018-20369/index.md)
```

## Sources

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

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