Dayforce Payroll flaws allow SQLi, XSS, path traversal
Free public brief. The indicators, the detections with Splunk and KQL already written, and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
CERT Polska coordinated disclosure of three unauthenticated vulnerabilities in Dayforce Payroll R2026.2.0, including blind SQL injection and path traversal.
CERT Polska has disclosed three vulnerabilities in Dayforce Payroll software, confirmed in version R2026.2.0, after unsuccessful attempts to contact the vendor. The most severe, CVE-2026-73640, is an unauthenticated Time-Based Blind SQL Injection in the password recovery functionality, where a GET request parameter is interpreted as part of a SQL predicate, allowing an attacker to extract data via timing-based inference without needing credentials.
CVE-2026-73641 is a Reflected XSS affecting multiple endpoints, allowing an attacker to craft a malicious URL that executes arbitrary JavaScript in a victim's browser when opened — typically used for session hijacking or credential phishing against authenticated users. CVE-2026-73642 is an unauthenticated Path Traversal vulnerability in the file download functionality, where a file path parameter can be set to an absolute local path, potentially allowing retrieval of arbitrary files from the server.
Because the vendor did not respond to disclosure attempts, no patch is confirmed available at time of publication, and other Dayforce Payroll versions beyond R2026.2.0 may also be affected. Defenders running Dayforce Payroll should treat all three issues as unauthenticated, remotely exploitable web application flaws, monitor for anomalous GET requests targeting password recovery and file download endpoints, restrict external exposure of the application where possible, and watch for vendor patch releases given the lack of confirmed vendor engagement.
Mentioned in this report
Source reporting: https://cert.pl/en/posts/2026/09/CVE-2026-73640
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections with the Splunk SPL and Microsoft KQL already written, the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 11,155 reports from 152 sources, 2,672 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs