CVE-2025-14590VulnerabilityPublished 13 Dec 2025Updated 24 Feb 2026

CVE-2025-14590: code-projects Prison Management System · SQL Injection

Affects code-projects Prison Management SystemSource 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 38% 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 13 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
GitHubasd1238525/cve`pkg:github/asd1238525/cve`Other threats	Affected =2.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

1. Immediate mitigation should include restricting access to the /admin/search1.php endpoint to trusted internal networks or VPNs to reduce exposure. 2. Implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns targeting the 'keyname' parameter. 3. Conduct thorough input validation and sanitization on all user-supplied parameters, especially 'keyname', using parameterized queries or prepared statements to prevent injection. 4. Monitor logs for unusual database query patterns or repeated failed attempts targeting the vulnerable endpoint. 5. Coordinate with the vendor or development team to obtain or develop an official patch or update for the Prison Management System. 6. If patching is delayed, consider isolating the affected system or deploying network segmentation to limit potential lateral movement. 7. Educate administrators about the vulnerability and ensure incident response plans include steps for SQL injection incidents. 8. Regularly back up critical data to enable recovery in case of data tampering or loss.

Description

A security vulnerability has been detected in code-projects Prison Management System 2.0. Impacted is an unknown function of the file /admin/search1.php. The manipulation of the argument keyname leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used.

Impact

The SQL injection vulnerability allows attackers to remotely execute arbitrary SQL queries on the backend database of the Prison Management System. This can lead to unauthorized disclosure of sensitive inmate and facility information, unauthorized modification or deletion of records, and potential disruption of system availability. Given the critical nature of prison management systems, such data breaches or operational disruptions could have severe consequences, including compromising inmate safety, violating privacy regulations, and undermining institutional trust. The lack of authentication and user interaction requirements increases the attack surface, enabling attackers to exploit the vulnerability at scale if the system is internet-facing or accessible via insecure networks. Organizations worldwide using this system risk data breaches, operational downtime, and regulatory penalties if the vulnerability is exploited.

Summary

CVE-2025-14590 is a SQL injection vulnerability identified in the code-projects Prison Management System version 2.0, specifically within the /admin/search1.php file. The vulnerability arises from improper input validation of the 'keyname' parameter, which is directly used in SQL queries without adequate sanitization or parameterization. This allows an unauthenticated remote attacker to inject arbitrary SQL commands, potentially manipulating the database to read, modify, or delete sensitive data. The vulnerability does not require any user interaction or privileges, making it remotely exploitable over the network. The CVSS 4.0 base score is 6.9 (medium), reflecting the moderate impact on confidentiality, integrity, and availability, with low complexity and no authentication required. Although no known exploits are currently active in the wild, the public disclosure of the vulnerability increases the likelihood of exploitation attempts. The affected product is a specialized prison management system, which typically handles sensitive inmate and facility data, making the impact of exploitation potentially severe. No official patches or fixes have been linked yet, so organizations must consider alternative mitigations to reduce risk.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats