Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-73640 – Unauthenticated Blind SQL Injection – Dayforce Payroll R2026.2.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-73640 is a time-based blind SQL injection vulnerability in the password recovery functionality of Dayforce Payroll. An unauthenticated remote attacker can inject arbitrary SQL through a GET request parameter to extract data from the backend database. The flaw carries a CVSS score of 9.3 (Critical) and requires no authentication or user interaction to exploit.

Technical details

  • Root cause: Improper neutralization of special elements used in an SQL command (CWE-89) — user-supplied input in a password recovery GET parameter is concatenated into a SQL query without adequate sanitization.
  • Trigger conditions: An attacker sends a crafted GET request to the password recovery endpoint with a parameter value containing a malicious SQL payload, which is interpreted as part of the SQL predicate.
  • Attack vector: Network-based, unauthenticated, low complexity, no user interaction required.
  • Impact: Time-based blind SQL injection allows an attacker to infer and extract data from the database (confidentiality impact: high) and potentially modify data (integrity impact: high) through timing side-channels; availability is not affected.

Affected software

  • Dayforce Payroll, confirmed on version R2026.2.0
  • The vendor could not be reached to confirm the fix status or scope, so other versions may also be affected

Severity

  • CVSS score: 9.3 (Critical)
  • CVSS v4.0 vector: 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

Mitigation and recommended actions

  • Immediate: No vendor patch is confirmed to be publicly available at the time of disclosure; the reporting party (CERT Polska) was unable to establish contact with Dayforce to confirm a fix. Organizations should contact Dayforce support directly to obtain a patched build or confirmation of remediation status.
  • If no patch is available:
    • Restrict and monitor access to the password recovery endpoint, especially from the public internet.
    • Deploy a web application firewall (WAF) rule to detect and block SQL injection patterns and time-based injection indicators (e.g., abnormal response delays) on password recovery requests.
    • Monitor logs for repeated or anomalous GET requests to the password recovery functionality with suspicious query parameters.
    • Limit direct internet exposure of the Dayforce Payroll instance where possible until remediation is confirmed.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge