# CVE-2023-5983: Information Disclosure in Botanik Software Pharmacy Automation

> An attacker can retrieve embedded sensitive personal information from the pharmacy automation software, exposing private data to unauthorized actors.

- **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:** 22 Nov 2023
- **Updated:** 20 May 2026
- **Also known as:** GHSA-769q-xhv3-qgqv

## What is CVE-2023-5983?

CVE-2023-5983 is a high-severity vulnerability in Botanik Software Pharmacy Automation, published on 22 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Exposure of Private Personal Information to an Unauthorized Actor vulnerability in Botanik Software Pharmacy Automation allows Retrieve Embedded Sensitive Data.

This issue affects Pharmacy Automation: before 2.1.133.0.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Botanikyazilim Pharmacy Automation.

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

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

## Is CVE-2023-5983 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5983 is a high-severity vulnerability in Botanik Software Pharmacy Automation, published on 22 Nov 2023. 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-2023-5983 in the wild and no public exploit code.

Affected product: Botanik Software Pharmacy Automation. 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-5983/ (Markdown: https://insights.sbomify.com/CVE-2023-5983/index.md)
```

## Sources

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

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