CVE-2026-38566

Published May 11, 2026 CVSS 3.1 · 8.1 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability exists because HireFlow version 1.2 omits CSRF token validation on all state‑changing POST endpoints. The affected endpoints include password change, candidate deletion, feedback submission, and interview scheduling. Without a CSRF token and without the SESSION_COOKIE_SAMESITE attribute, a malicious page can trigger these actions silently when an authenticated user visits it, allowing the attacker to change the victim’s password, delete records, or submit arbitrary data. The weakness leads to loss of confidentiality, integrity, and availability of user data.

Affected Systems

HireFlow v1.2, an interview management system built in Python, is the only affected product. All users logged into this version are vulnerable to the described attacks.

Risk and Exploitability

The EPSS score is < 1%, indicating a low likelihood of exploitation, and it is not listed in CISA’s KEV catalog, indicating it is not currently known to be actively exploited. However, the attack surface is high because it requires only that an authenticated user visit a malicious webpage, which can be achieved through phishing or compromised content. The CVSS score is 8.1, indicating a high severity.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Implement CSRF token validation on all POST endpoints and validate the token on the server side
  • Set the SESSION_COOKIE_SAMESITE attribute to "Lax" or "Strict" to enforce browser‑level CSRF protection
  • Deploy a framework‑level CSRF protection mechanism such as anti‑CSRF libraries or built‑in platform features

Generated by OpenCVE AI on May 12, 2026 at 16:11 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Title Missing CSRF Protection Allows Sensitive Data Modification
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Stratonwebdesigners
Stratonwebdesigners hireflow
Vendors & Products Stratonwebdesigners
Stratonwebdesigners hireflow
Type Values Removed Values Added
Title Missing CSRF Protection Allows Sensitive Data Modification
Weaknesses CWE-352
Type Values Removed Values Added
Description 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.
References
Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
May 12, 2026, 1:43 PM
Reserved
Apr 6, 2026, 12:00 AM
Status
Deferred
Published
May 11, 2026, 6:16 PM
Modified
Jun 17, 2026, 10:41 AM