Database disclosure via password-recovery SQL predicate injection
Published Sep 28, 2026 · Updated Sep 28, 2026
Time-based blind SQL injection in Dayforce Payroll R2026.2.0 allows remote attackers to infer data via password recovery GET requests. The password-recovery handler treats a crafted GET parameter as part of a SQL predicate, allowing response delays to encode results from injected queries. Exposure requires a tenant with self-service password reset enabled; the supplied advisory confirms only R2026.2.0 and does not identify the parameter.
Summary
What happened
Time-based blind SQL injection in Dayforce Payroll R2026.2.0 allows remote attackers to infer data via password recovery GET requests. The password-recovery handler treats a crafted GET parameter as part of a SQL predicate, allowing response delays to encode results from injected queries. Exposure requires a tenant with self-service password reset enabled; the supplied advisory confirms only R2026.2.0 and does not identify the parameter.
The record
- CVE
- CVE-2026-73640
- Published
- Sep 28, 2026
- Updated
- Sep 28, 2026
- Vendor
- Dayforce
- Product
- Dayforce Payroll
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 28, 2026CVE publishedPublication date reported by the CVE source.
- Sep 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=R2026.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started