CVE-2026-38567
Received Received - Intake
SQL Injection in HireFlow v1.2

Publication date: 2026-05-11

Last updated on: 2026-05-11

Assigner: MITRE

Description
HireFlow v1.2 is vulnerable to SQL injection in the /login and /search endpoints. User-supplied input is concatenated directly into SQL queries without parameterization. An unauthenticated attacker can bypass authentication by supplying a crafted username (e.g. admin'--) or extract the full contents of the database including user credentials via UNION-based injection at the /search endpoint.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-11
Last Modified
2026-05-11
Generated
2026-06-21
AI Q&A
2026-05-11
EPSS Evaluated
2026-06-20
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
hireflow hireflow 1.2
stratonwebdesigners hireflow to 1.3 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Compliance Impact

The SQL injection vulnerability in HireFlow v1.2 allows an unauthenticated attacker to bypass authentication and extract the full contents of the database, including user credentials. This exposure of sensitive personal data can lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require the protection of personal and sensitive information against unauthorized access and breaches.

Specifically, unauthorized access to user credentials and other personal data can result in violations of confidentiality and data integrity requirements mandated by these standards, potentially leading to legal and financial consequences for organizations using the affected software.

Executive Summary

CVE-2026-38567 is a SQL injection vulnerability in HireFlow Interview Management System v1.2 affecting the /login and /search endpoints.

User input is directly concatenated into SQL queries without proper parameterization, allowing an attacker to manipulate the queries.

An unauthenticated attacker can bypass authentication by injecting a crafted username (e.g., admin'--) into the /login endpoint, which comments out the password check and grants access to any account, including admin.

Additionally, the attacker can extract the full database contents, including usernames and password hashes, via a UNION-based SQL injection in the /search endpoint.

Impact Analysis

This vulnerability can have severe impacts including unauthorized access to any user account, including administrative accounts, without needing valid credentials.

An attacker can also exfiltrate sensitive data such as usernames and password hashes from the database, potentially leading to further compromise.

Such unauthorized access and data leakage can result in loss of confidentiality, integrity, and trust in the affected system.

Detection Guidance

This vulnerability can be detected by attempting SQL injection payloads against the /login and /search endpoints of the HireFlow v1.2 application.

  • For the /login endpoint, try sending a username parameter with a value like: admin'-- to see if authentication can be bypassed.
  • For the /search endpoint, test for UNION-based SQL injection by sending a payload such as: ' UNION SELECT username, password, null FROM users-- and check if database contents are returned.

These tests can be performed using tools like curl or specialized SQL injection testing tools.

  • Example curl command for /login test: curl -X POST -d "username=admin'--&password=anything" http://target/hireflow/login
  • Example curl command for /search test: curl -G --data-urlencode "query=' UNION SELECT username, password, null FROM users--" http://target/hireflow/search
Mitigation Strategies

Immediate mitigation steps include:

  • Upgrade HireFlow to version 1.3 or later, where the vulnerability has been patched.
  • If upgrading is not immediately possible, restrict access to the /login and /search endpoints using network controls or web application firewalls to block malicious input.
  • Implement input validation and sanitization to prevent SQL injection payloads from reaching the database.
  • Review and modify the application code to replace raw SQL string concatenation with parameterized queries or prepared statements.
  • Consider using an ORM like SQLAlchemy which handles parameterization by default to prevent SQL injection.
Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-38567. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart