CVE-2026-38566: HireFlow · Cross-Site Request Forgery (CSRF)
Affects HireFlowSource CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubstratonwebdesigners/HireFlowpkg:github/stratonwebdesigners/HireFlowOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official fix is available, users should limit exposure by avoiding untrusted links while authenticated in HireFlow. Implementing CSRF token validation on all state-changing endpoints and configuring the SESSION_COOKIE_SAMESITE attribute are recommended mitigations once a patch is released.
Description
HireFlow version 1.2 lacks CSRF token validation on all state-changing POST endpoints, including password changes, candidate deletions, feedback submissions, and interview scheduling. Additionally, the SESSION_COOKIE_SAMESITE attribute is not configured, removing a browser-level defense against CSRF attacks. An attacker who tricks an authenticated user into visiting a malicious page could perform unauthorized actions on the victim's behalf. This vulnerability has a high severity score of 8.1 but currently has no known exploits in the wild and no official patch or remediation guidance published.