dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-38566

HIGH · 8.1 CVSS v3.1 Published 2026-05-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
HireFlow v1.2 does not implement CSRF token validation on any state-changing POST endpoint. All forms (password change at /profile, candidate deletion at /candidates/delete/<id>, feedback submission at /feedback/add/<id>, interview scheduling at /interviews/add) are vulnerable to CSRF. An attacker who can trick an authenticated user into visiting a malicious page can silently change the victim's password, delete records, or inject arbitrary data on their behalf. The SESSION_COOKIE_SAMESITE attribute is also not configured, removing the browser-level CSRF defense.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

HireFlow v1.2 lacks CSRF token validation on all state-changing POST endpoints including password change, candidate deletion, feedback submission, and interview scheduling. Additionally, the SESSION_COOKIE_SAMESITE attribute is not configured, removing browser-level CSRF protection. Attackers can trick authenticated users into unknowingly performing these actions.

MitigationImplement CSRF token validation on all POST endpoints using a standard CSRF library and configure SESSION_COOKIE_SAMESITE to 'Lax' or 'Strict' in the application settings.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed HireFlow version
    Locate the application version file, banner, or admin interface that displays the current HireFlow version number
    Affected if The installed version is HireFlow v1.2 exactly
  2. Inspect password change endpoint for CSRF token
    Submit a POST request to the password change endpoint (such as /user/password or /settings/password) and examine whether the request body or headers include a CSRF token parameter or header
    Affected if No CSRF token is required or validated on the password change POST request
  3. Inspect candidate deletion endpoint for CSRF token
    Submit a POST request to the candidate deletion endpoint (such as /candidates/delete or /candidates/{id}/delete) and examine whether a CSRF token is required or validated
    Affected if No CSRF token is required or validated on candidate deletion POST requests
  4. Inspect feedback submission endpoint for CSRF token
    Submit a POST request to the feedback or review submission endpoint and examine whether a CSRF token is present and validated
    Affected if No CSRF token is required or validated on feedback submission POST requests
  5. Inspect interview scheduling endpoint for CSRF token
    Submit a POST request to the interview scheduling or calendar endpoint and examine whether a CSRF token is present and validated
    Affected if No CSRF token is required or validated on interview scheduling POST requests
  6. Check SESSION_COOKIE_SAMESITE configuration
    Locate the application session configuration file or settings and verify whether SESSION_COOKIE_SAMESITE is set to 'Lax', 'Strict', or any value
    Affected if SESSION_COOKIE_SAMESITE is not configured or is set to None/Null, leaving CSRF protection at the browser level disabled

A user is affected if they run HireFlow v1.2 and any of the state-changing POST endpoints lack CSRF token validation or SESSION_COOKIE_SAMESITE is unset.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement CSRF token validation on all POST endpoints using a standard CSRF library and configure SESSION_COOKIE_SAMESITE to 'Lax' or 'Strict' in the application settings.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-38566 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-38566 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data