# CVE-2024-50344: I, Librarian has a Stored XSS vulnerability in Supplemental Files

> Attackers can execute arbitrary JavaScript in the victim's browser by uploading malicious supplemental files due to broken MIME type validation.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Oct 2024
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-c2rm-w62w-5xmj

## What is CVE-2024-50344?

CVE-2024-50344 is a medium-severity cross-site scripting vulnerability in mkucej i-librarian-free, published on 30 Oct 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

I, Librarian is an open-source version of a PDF managing SaaS. Supplemental Files are allowed to be viewed in the browser, only if they have a white-listed MIME type. Unfortunately, this logic is broken, thus allowing unsafe files containing Javascript to be executed with the application context. An attacker can exploit this vulnerability by uploading a supplementary file that contains a malicious code or script. This code will then be executed when the file is loaded in the browser. The vulnerability was fixed in version 5.11.2.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

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


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

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

## Is CVE-2024-50344 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-50344 is a medium-severity cross-site scripting vulnerability in mkucej i-librarian-free, published on 30 Oct 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-50344 in the wild and no public exploit code.

Affected product: mkucej i-librarian-free. 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-50344/ (Markdown: https://insights.sbomify.com/CVE-2024-50344/index.md)
```

## Sources

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

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