CVE-2025-14193
BaseFortify
Publication date: 2025-12-07
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| carmelogarcia | employee_profile_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Employee Profile Management System 1.0, specifically in the /view_personnel.php file. It allows an attacker to manipulate the 'per_id' argument to perform SQL injection, which means the attacker can execute unauthorized SQL commands on the database remotely.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to remotely execute SQL injection attacks, potentially leading to unauthorized access, modification, or deletion of sensitive employee data stored in the system. This can compromise the integrity and confidentiality of the data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access to sensitive personnel data through SQL injection, leading to potential data disclosure, modification, or deletion. Such unauthorized access and data breaches can result in non-compliance with data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information. Therefore, exploitation of this vulnerability could lead to violations of these standards due to compromised confidentiality, integrity, and availability of protected data. [1, 2, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable endpoints such as `view_personnel.php` for SQL injection on the `per_id` parameter. You can use manual HTTP requests with SQL injection payloads, for example: `GET /employee_profile/view_personnel.php?per_id=1' OR '1'='1--` to see if the system returns all personnel records instead of one. Automated tools like sqlmap can also be used to detect and exploit the vulnerability, for example: `sqlmap -u "http://localhost/employee_profile/view_personnel.php?per_id=1" -p per_id --dbs`. Additionally, intercepting HTTP requests with tools like Burp Suite or Fiddler to inject SQL payloads into parameters can help identify the flaw. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement proper use of parameterized queries with bound parameters instead of concatenating user inputs directly into SQL statements. For example, replace insecure code like `$sql = "SELECT * FROM personnel WHERE per_id = " . $_GET['per_id'];` with parameterized queries such as `$stmt = $pdo->prepare("SELECT * FROM personnel WHERE per_id = :id"); $stmt->execute([':id' => $_GET['per_id']]);`. 2) Validate and sanitize all external inputs, enforcing integer-only checks for ID parameters (`per_id`, `dept_id`, `position_id`, `rank_id`). 3) Whitelist allowed formats for parameters like `term` (e.g., `YYYY-S`). 4) If possible, replace the affected software with an alternative product. 5) Monitor and restrict access to vulnerable endpoints until patches or fixes are applied. [1, 2]