CVE-2025-15195VulnerabilityPublished 29 Dec 2025Updated 24 Feb 2026

CVE-2025-15195: code-projects Assessment Management · SQL Injection

Affects code-projects Assessment ManagementSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 18:53 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% 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 29 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 2026-10-25.

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
GitHublimingqian123/CVE`pkg:github/limingqian123/CVE`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-15195, organizations should first check for any official patches or updates from the vendor and apply them immediately once available. In the absence of patches, implement strict input validation and sanitization on the 'linked[]' parameter in /admin/add-module.php to prevent SQL injection. Employ web application firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting this parameter. Restrict access to the administrative interface by IP whitelisting or VPN to reduce exposure. Conduct thorough code reviews and penetration testing focused on SQL injection vectors in the application. Additionally, ensure database accounts used by the application follow the principle of least privilege to limit the impact of any successful injection. Monitor logs for suspicious database queries or unusual activity related to the vulnerable endpoint. Finally, consider isolating or segmenting the affected system within the network to contain potential breaches.

Description

A vulnerability was determined in code-projects Assessment Management 1.0. Affected by this issue is some unknown functionality of the file /admin/add-module.php. This manipulation of the argument linked[] causes sql injection. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized.

Impact

The impact of this SQL injection vulnerability is significant for organizations using code-projects Assessment Management 1.0. Successful exploitation can lead to unauthorized access to sensitive data stored in the backend database, including potentially user credentials, assessment data, or administrative information. Attackers may alter or delete data, undermining data integrity and availability. This could disrupt assessment operations, cause data loss, or facilitate further attacks such as privilege escalation or lateral movement within the network. Since the vulnerability requires no authentication and can be exploited remotely, it poses a high risk of compromise, especially in environments where the affected software is exposed to untrusted networks. Organizations handling sensitive educational or assessment data may face regulatory compliance issues, reputational damage, and operational downtime if exploited.

Summary

CVE-2025-15195 identifies a SQL injection vulnerability in the code-projects Assessment Management software, version 1.0. The vulnerability exists in the /admin/add-module.php script, where the 'linked[]' parameter is not properly sanitized or validated before being used in SQL queries. This allows an unauthenticated remote attacker to inject arbitrary SQL commands, potentially manipulating the backend database. The attack vector requires no user interaction and no privileges, making it remotely exploitable over the network. The vulnerability can lead to unauthorized data disclosure, data modification, or deletion, and possibly full system compromise depending on the database permissions. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and partial impacts on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). The vulnerability was reserved on 2025-12-28 and published on 2025-12-29, with no patches currently available and no known active exploits in the wild. Given the public disclosure, the risk of exploitation may increase rapidly. The lack of CWE identifiers suggests limited detailed public analysis, but the nature of SQL injection is well understood and widely exploitable if unmitigated.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats