# CVE-2024-36049: Hardcoded credentials in n/a

> Attackers can intercept unencrypted traffic to steal payroll credentials and impersonate users due to hardcoded credentials in the Windows client.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 May 2024
- **Updated:** 13 Feb 2025

## What is CVE-2024-36049?

CVE-2024-36049 is a medium-severity vulnerability in n/a, published on 24 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Aptos Wisal payroll accounting before 7.1.6 uses hardcoded credentials in the Windows client to fetch the complete list of usernames and passwords from the database server, using an unencrypted connection. This allows attackers in a machine-in-the-middle position read and write access to personally identifiable information (PII) and especially payroll data and the ability to impersonate legitimate users with respect to the audit log.

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

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


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

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

## Is CVE-2024-36049 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36049 is a medium-severity vulnerability in n/a, published on 24 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36049 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-2024-36049/ (Markdown: https://insights.sbomify.com/CVE-2024-36049/index.md)
```

## Sources

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

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