# CVE-2022-28991: Information disclosure in n/a

> Attackers can access sensitive files in Multi Store Inventory Management System, leading to information disclosure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 20 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-258j-hjx4-w4m2

## What is CVE-2022-28991?

CVE-2022-28991 is a high-severity vulnerability in n/a, published on 20 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multi Store Inventory Management System v1.0 was discovered to contain an information disclosure vulnerability which allows attackers to access sensitive files.

Weakness: CWE-425 (Direct Request)

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

It affects 1 product.


Products: Bdtask Multi Store Inventory Management System.

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

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

## Is CVE-2022-28991 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-28993](https://insights.sbomify.com/CVE-2022-28993/): Missing authorization in n/a (critical 9.8)
- [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-2997](https://insights.sbomify.com/CVE-2024-2997/): Bdtask Multi-Store Inventory Management System 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-2022-28991 and fix it if it is affected.

What it is: CVE-2022-28991 is a high-severity vulnerability in n/a, published on 20 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-28991 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-2022-28991/ (Markdown: https://insights.sbomify.com/CVE-2022-28991/index.md)
```

## Sources

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

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