# CVE-2023-45540: Cross-site scripting in n/a

> Remote attackers can execute arbitrary HTML code via the comment field in Jorani Leave Management System, potentially compromising user sessions.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2023
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-q6rf-xpm8-9wqx

## What is CVE-2023-45540?

CVE-2023-45540 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Jorani Leave Management System 1.0.3 allows a remote attacker to execute arbitrary HTML code via a crafted script to the comment field of the List of Leave requests page.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2023-45540?

It affects 1 product.


Products: Jorani Leave Management System.

## How do I fix CVE-2023-45540?

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

## Is CVE-2023-45540 being exploited?

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

Public exploit code:

- CVE-2023-45540 Jorani Leave Management System v1.0.3 –  HTML Injection (github_poc): https://github.com/SoundarXploit/CVE-2023-45540

## Other vulnerabilities in n/a

- [CVE-2023-48205](https://insights.sbomify.com/CVE-2023-48205/): Other in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-45540 and fix it if it is affected.

What it is: CVE-2023-45540 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Oct 2023. 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-2023-45540 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-2023-45540/ (Markdown: https://insights.sbomify.com/CVE-2023-45540/index.md)
```

## Sources

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

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