# CVE-2024-2997: Bdtask Multi-Store Inventory Management System cross site scripting

> Remote attackers can inject malicious scripts via inventory fields, potentially compromising user sessions in the Bdtask Multi-Store Inventory Management System.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/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:** No
- **Published:** 27 Mar 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-rrh2-f5v6-9vq7

## What is CVE-2024-2997?

CVE-2024-2997 is a low-severity cross-site scripting vulnerability in Bdtask Multi-Store Inventory Management System, published on 27 Mar 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in Bdtask Multi-Store Inventory Management System up to 20240320. It has been declared as problematic. Affected by this vulnerability is an unknown functionality. The manipulation of the argument Category Name/Model Name/Brand Name/Unit Name leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-258199. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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

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

It affects 1 product.


Products: Bdtask Multi Store Inventory Management System.

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

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

## Is CVE-2024-2997 being exploited?

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

Public exploit code:

- The tool helps in quickly identifying vulnerabilities by examining a comprehensive list of potential paths on a website, making it useful for security assessments. (github_poc): https://github.com/lfillaz/CVE-2024-2997
-  The tool helps in quickly identifying vulnerabilities by examining a comprehensive list of potential paths on a website, making it useful for security assessments.  (github_poc): https://github.com/0xUho/CVE-2024-2997

## Other vulnerabilities in Bdtask Multi-Store Inventory Management System

- [CVE-2022-28993](https://insights.sbomify.com/CVE-2022-28993/): Missing authorization in n/a (critical 9.8)
- [CVE-2022-28991](https://insights.sbomify.com/CVE-2022-28991/): Information disclosure in n/a (high 7.5)
- [CVE-2024-2996](https://insights.sbomify.com/CVE-2024-2996/): Bdtask Multi-Store Inventory Management System Page Title cross site scripting (low 2.4)
- [CVE-2024-2998](https://insights.sbomify.com/CVE-2024-2998/): Bdtask Multi-Store Inventory Management System Store Update Page cross site scripting (low 2.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2997 is a low-severity cross-site scripting vulnerability in Bdtask Multi-Store Inventory Management System, published on 27 Mar 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-2997 in the wild and no public exploit code.

Affected product: Bdtask Multi-Store Inventory Management System. 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-2997/ (Markdown: https://insights.sbomify.com/CVE-2024-2997/index.md)
```

## Sources

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

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