# CVE-2024-4996: Hardcoded Password in Wapro ERP Desktop

> Attackers can access sensitive database data using a hardcoded administrator password present in all installations of Wapro ERP Desktop.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/AU:Y/R:I/V:C/RE:M/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2024
- **Updated:** 7 Oct 2025
- **Also known as:** GHSA-xw4r-rf67-rf6g

## What is CVE-2024-4996?

CVE-2024-4996 is a critical vulnerability in Asseco Business Solutions S.A. Wapro ERP Desktop, published on 18 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of a hard-coded password for a database administrator account created during Wapro ERP installation allows an attacker to retrieve embedded sensitive data stored in the database. The password is same among all Wapro ERP installations. This issue affects Wapro ERP Desktop versions before 8.90.0.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

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


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

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

## Is CVE-2024-4996 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4996 is a critical vulnerability in Asseco Business Solutions S.A. Wapro ERP Desktop, published on 18 Dec 2024. 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-2024-4996 in the wild and no public exploit code.

Affected product: Asseco Business Solutions S.A. Wapro ERP Desktop. 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-4996/ (Markdown: https://insights.sbomify.com/CVE-2024-4996/index.md)
```

## Sources

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

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