CVE-2025-6351
BaseFortify
Publication date: 2025-06-20
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 |
|---|---|---|
| clivedelacruz | employee_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
Can you explain this vulnerability to me?
CVE-2025-6351 is a critical SQL injection vulnerability in the itsourcecode Employee Record Management System version 1.0. It occurs in the /editprofile.php file where the emp1name parameter is not properly validated or sanitized. This allows an attacker to inject malicious SQL code into the database queries, potentially compromising the system's security and data integrity. The vulnerability can be exploited remotely and may require an authenticated session depending on the source, enabling attackers to manipulate SQL queries and gain unauthorized access or control. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, leakage of sensitive data, data tampering, full system control, and service disruption. Attackers can manipulate SQL queries to extract or modify confidential information, potentially compromising the confidentiality, integrity, and availability of the system. Exploitation may be possible remotely and, according to some sources, may require an authenticated session. The impact is critical and can severely affect the security posture of the affected system. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /editprofile.php endpoint for SQL injection in the emp1name parameter. One method is to use time-based blind SQL injection payloads, such as injecting: emp1name=ABC' AND (SELECT 5922 FROM (SELECT(SLEEP(5)))iCqL) AND 'wThK'='wThK' to observe delays indicating vulnerability. Automated tools like sqlmap can be used with a valid authenticated session cookie (e.g., PHPSESSID) to test and enumerate the database. Additionally, Google Dorking with queries like inurl:editprofile.php can help locate potentially vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the emp1name parameter, and minimizing database user permissions to limit potential damage. Conducting regular security audits to detect and remediate vulnerabilities promptly is also recommended. Since the vulnerability requires authenticated access, ensuring strong session management and monitoring for suspicious activity can help. If possible, replacing the affected product with a secure alternative is advised. [2, 3]