CVE-2025-14285VulnerabilityPublished 9 Dec 2025Updated 24 Feb 2026

CVE-2025-14285: code-projects Employee Profile Management System · SQL Injection

Affects code-projects Employee Profile Management SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projects Employee Profile Management System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2025-14285, organizations should immediately implement input validation and sanitization for all user-supplied data, especially the per_id parameter in edit_personnel.php. Employing parameterized queries or prepared statements will prevent SQL injection by separating code from data. Restrict database user permissions to the minimum necessary to limit the impact of any successful injection. Monitor logs for suspicious SQL query patterns or unexpected database errors that could indicate exploitation attempts. If patches or updates become available from the vendor, apply them promptly. In the absence of official patches, consider deploying web application firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting this parameter. Conduct regular security assessments and code reviews to identify and remediate similar vulnerabilities. Additionally, educate developers on secure coding practices to prevent future injection flaws.

Description

A vulnerability was found in code-projects Employee Profile Management System 1.0. Affected is an unknown function of the file edit_personnel.php. The manipulation of the argument per_id results in sql injection. The attack can be launched remotely. The exploit has been made public and could be used.

Impact

The SQL injection vulnerability in the Employee Profile Management System can have serious consequences for organizations using this software. Exploitation could allow attackers to access sensitive employee data, modify or delete records, and potentially escalate privileges within the system. This could lead to data breaches, loss of data integrity, and disruption of HR operations. The remote and unauthenticated nature of the attack increases the risk, as attackers do not need valid credentials or user interaction to exploit the flaw. Organizations could face regulatory penalties if personal data is exposed, reputational damage, and operational downtime. The medium severity rating reflects the balance between ease of exploitation and the limited scope of impact, but the presence of publicly available exploit code elevates the urgency for mitigation. The threat is particularly impactful for enterprises relying heavily on this system for employee management, especially those with large or sensitive personnel databases.

Summary

CVE-2025-14285 is a SQL injection vulnerability identified in the Employee Profile Management System version 1.0 developed by code-projects. The vulnerability resides in the edit_personnel.php script, where the per_id parameter is improperly sanitized, allowing an attacker to inject malicious SQL code. This injection flaw enables remote attackers to manipulate backend SQL queries without requiring authentication or user interaction, potentially leading to unauthorized data disclosure, modification, or deletion. The vulnerability has been assigned a CVSS 4.0 base score of 6.9, reflecting medium severity, with an attack vector of network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), and no user interaction (UI:N). The impact on confidentiality, integrity, and availability is low to limited, but exploitation could still lead to significant data exposure or corruption. Although no known exploits are currently active in the wild, the public availability of exploit code increases the likelihood of future attacks. The lack of patches or official fixes at the time of publication necessitates immediate mitigation efforts by affected organizations. This vulnerability highlights the critical need for secure coding practices, especially input validation and the use of parameterized queries to prevent SQL injection attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:54 UTC

Technical details

References

Community reviews

Related threats