# CVE-2026-73640: Time-based SQL Injection in Dayforce ESS Excelity

> Unauthenticated attackers can execute time-based blind SQL injection via password recovery parameters to read sensitive data.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-wrm6-gm2g-4hgx

## What is CVE-2026-73640?

CVE-2026-73640 is a critical SQL injection vulnerability in Dayforce ESS Excelity, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dayforce ESS Excelity is vulnerable to Time Based-Blind SQL Injection in password recovery functionality. The unauthenticated attacker can prepare GET request with one of the parameters filled in with an arbitrary SQL query. The parameter is interpreted as part of SQL predicate resulting in Time-Based Blind SQL Injection.
This issue was fixed in version V3.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-73640?


## How do I fix CVE-2026-73640?

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

## Is CVE-2026-73640 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73640 and fix it if it is affected.

What it is: CVE-2026-73640 is a critical SQL injection vulnerability in Dayforce ESS Excelity, published on 28 Sep 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-2026-73640 in the wild and no public exploit code.

Affected product: Dayforce ESS Excelity. 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-2026-73640/ (Markdown: https://insights.sbomify.com/CVE-2026-73640/index.md)
```

## Sources

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

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