Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14223: SQL Injection in code-projects Simple Leave Manager

0
Medium
VulnerabilityCVE-2025-14223cvecve-2025-14223
Published: Mon Dec 08 2025 (12/08/2025, 08:02:06 UTC)
Source: CVE Database V5
Vendor/Project: code-projects
Product: Simple Leave Manager

Description

A vulnerability has been found in code-projects Simple Leave Manager 1.0. Affected by this vulnerability is an unknown functionality of the file /request.php. Such manipulation of the argument staff_id leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

AI-Powered Analysis

AILast updated: 12/08/2025, 08:19:41 UTC

Technical Analysis

CVE-2025-14223 identifies a SQL injection vulnerability in version 1.0 of the Simple Leave Manager software developed by code-projects. The vulnerability resides in the /request.php script, specifically in the handling of the staff_id parameter. Due to insufficient input validation or sanitization, an attacker can craft malicious input that alters the intended SQL query logic, enabling unauthorized database queries. This can lead to unauthorized data retrieval, modification, or deletion within the application's database. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The CVSS 4.0 base score is 6.9, reflecting medium severity with network attack vector, low complexity, and no privileges or user interaction needed. The impact on confidentiality, integrity, and availability is limited but non-negligible, as indicated by the CVSS vector components (VC:L, VI:L, VA:L). No patches or fixes have been publicly released yet, and no known exploits are currently observed in the wild. The disclosure date is December 8, 2025, indicating a recent discovery. The affected product is a specialized leave management system likely deployed in HR environments to manage employee leave requests and records. Exploitation could expose sensitive employee data or disrupt leave management operations.

Potential Impact

For European organizations, the impact of this vulnerability can be significant, especially for those handling sensitive employee data subject to GDPR and other privacy regulations. Unauthorized access or manipulation of leave records could lead to data breaches, exposing personally identifiable information (PII) and potentially resulting in regulatory fines and reputational damage. Operationally, exploitation could disrupt HR processes, affecting workforce management and payroll accuracy. The medium severity suggests that while the vulnerability does not allow full system compromise, it still poses a tangible risk to data confidentiality and integrity. Organizations using Simple Leave Manager version 1.0 must consider the risk of targeted attacks, particularly from insiders or external threat actors aiming to access or alter HR data. The lack of authentication requirement lowers the barrier for attackers, increasing the likelihood of exploitation if the software is internet-facing or accessible within internal networks. Given the public disclosure, the risk of exploit development and subsequent attacks will likely increase over time.

Mitigation Recommendations

1. Immediately audit all instances of Simple Leave Manager version 1.0 to identify affected systems. 2. Implement strict input validation and sanitization on the staff_id parameter in /request.php, preferably using parameterized queries or prepared statements to prevent SQL injection. 3. If available, apply vendor patches or updates addressing this vulnerability as soon as they are released. 4. Restrict network access to the application, limiting exposure to trusted internal networks or VPNs to reduce remote exploitation risk. 5. Monitor application logs for suspicious queries or unusual activity targeting the staff_id parameter. 6. Conduct security testing, including automated and manual penetration tests, focusing on SQL injection vectors. 7. Educate HR and IT staff about the vulnerability and the importance of timely patching and access controls. 8. Consider deploying Web Application Firewalls (WAFs) with rules to detect and block SQL injection attempts targeting this endpoint. 9. Review and enhance database user permissions to minimize the impact of any successful injection, following the principle of least privilege. 10. Prepare an incident response plan to quickly address any detected exploitation attempts.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-12-07T15:33:10.940Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69368a07ddfbd9e35f898b80

Added to database: 12/8/2025, 8:19:19 AM

Last enriched: 12/8/2025, 8:19:41 AM

Last updated: 12/9/2025, 6:14:15 PM

Views: 19

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats