# CVE-2024-23564: Business logic in Aftermarket EPC

> Attackers can steal user passwords by manipulating email requests due to missing validation, leading to account takeover.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-wmr2-f2gc-hxq6

## What is CVE-2024-23564?

CVE-2024-23564 is a critical vulnerability in HCL Software Aftermarket EPC, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HCL Aftermarket EPC is affected by Business Logic Vulnerability using which a non valid user of the application can obtain passwords from the server and redirect them to their own email address by manipulating the server's response. The application includes checks in the initial requests to verify the validity of the provided UserId, but similar validation is not applied to Email requests when sending passwords to user emails.

Weakness: CWE-326 (Inadequate Encryption Strength)

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


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

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

## Is CVE-2024-23564 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-23564 is a critical vulnerability in HCL Software Aftermarket EPC, published on 17 Jul 2026. 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-23564 in the wild and no public exploit code.

Affected product: HCL Software Aftermarket EPC. 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-23564/ (Markdown: https://insights.sbomify.com/CVE-2024-23564/index.md)
```

## Sources

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

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