CVE-2025-6610
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-06-25

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was found in itsourcecode Employee Management System up to 1.0. It has been classified as critical. This affects an unknown part of the file /admin/editempprofile.php. The manipulation of the argument FirstName leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-06-25
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2025-06-25
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
clivedelacruz employee_management_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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-6610 is a critical SQL injection vulnerability in the itsourcecode Employee Management System version 1.0, specifically in the /admin/editempprofile.php file. The vulnerability occurs because the 'FirstName' parameter is not properly sanitized or validated, allowing an authenticated attacker (with valid admin credentials) to inject malicious SQL code. This can be done remotely after logging in, enabling the attacker to manipulate database queries. [1, 2, 3]


How can this vulnerability impact me? :

This vulnerability can severely impact system security by allowing attackers to access, modify, or delete sensitive data in the database. It can lead to unauthorized database access, leakage of confidential information, data tampering, full system control, and potential disruption of services. Exploitation requires valid administrator credentials but can be performed remotely, posing a significant risk to data integrity, confidentiality, and availability. [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 /admin/editempprofile.php endpoint for SQL injection in the 'FirstName' parameter. Detection requires authenticated access with valid admin credentials (e.g., username: admin, password: Test@123) and a valid session cookie (PHPSESSID). One can use tools like sqlmap to automate detection, providing the session cookie and targeting the vulnerable parameter. An example of a manual test payload is a time-based blind SQL injection such as: FirstName=test' AND (SELECT 6838 FROM (SELECT(SLEEP(5)))ytmD) AND 'Udnm'='Udnm. Additionally, vulnerable targets can be identified using Google dorking with the query: "inurl:admin/editempprofile.php". [2, 3]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, 2) Applying strict input validation and filtering on the 'FirstName' parameter to ensure it conforms to expected formats, 3) Minimizing database user permissions to the least required privileges and avoiding use of high-privilege accounts for routine operations, and 4) Conducting regular security audits to detect and remediate vulnerabilities promptly. Since no known countermeasures or patches are documented, consider replacing the affected product with a secure alternative if possible. [2, 3]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart