CVE-2025-14285
BaseFortify
Publication date: 2025-12-09
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 |
|---|---|---|
| code-projects | employee_profile_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthorized access, data leakage, and data tampering due to SQL injection, which compromises data confidentiality, integrity, and availability. Such impacts can lead to non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of sensitive personal and health information. Therefore, exploitation of this vulnerability could result in violations of these regulations by exposing or altering protected data. [1, 2, 3]
Can you explain this vulnerability to me?
This vulnerability is a SQL injection found in the edit_personnel.php file of the code-projects Employee Profile Management System 1.0. It occurs due to improper handling of the per_id argument, allowing an attacker to manipulate the SQL query. The attack can be launched remotely and the exploit is publicly available.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute arbitrary SQL commands on the database, potentially leading to unauthorized data access, data modification, or deletion. Since it can be exploited remotely without authentication, it poses a significant risk to the confidentiality, integrity, and availability of the system's data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'per_id' parameter in the 'edit_personnel.php' file for SQL injection using time-based blind SQL injection techniques. A proof-of-concept Python script named 'poc_version_sqli.py' is available, which performs adaptive time-based blind SQL injection by injecting payloads that cause delays when certain conditions are met. The script measures response times to infer database information, indicating vulnerability. Example usage includes specifying the target URL, parameter name, delay duration, and other options. Additionally, attackers can identify vulnerable targets using Google dorking with queries like 'inurl:edit_personnel.php'. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include employing prepared statements with parameter binding to separate SQL code from user input, implementing rigorous input validation and filtering to ensure inputs conform to expected formats, and minimizing database user permissions by avoiding high-privilege accounts for routine operations. Since no known countermeasures or mitigations have been documented, replacing the affected component with an alternative product is also suggested to secure the system. [1, 3]