CVE-2025-14216VulnerabilityPublished 8 Dec 2025

CVE-2025-14216: code-projects Currency Exchange System · SQL Injection

Affects code-projects Currency Exchange SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 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 8 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
code-projects Currency Exchange System	Affected =1.0	Fixed in–

AI-suggested

1. Immediately audit all instances of the code-projects Currency Exchange System version 1.0 to identify affected deployments. 2. Implement input validation and sanitization on the 'ID' parameter in /viewserial.php to reject or properly escape malicious input. 3. Refactor database queries to use parameterized statements or prepared queries to eliminate direct injection vectors. 4. Deploy Web Application Firewalls (WAFs) with rules targeting SQL injection patterns specific to this vulnerability as a temporary protective measure. 5. Monitor database logs and application logs for unusual query patterns or errors indicative of injection attempts. 6. Restrict database user permissions to the minimum necessary to limit potential damage if exploited. 7. Engage with the vendor or community to obtain or develop official patches or updates addressing this vulnerability. 8. Conduct security awareness training for developers to prevent similar vulnerabilities in future releases. 9. Consider isolating or segmenting the vulnerable application within the network to reduce exposure. 10. Prepare incident response plans to quickly address potential exploitation events.

Description

CVE-2025-14216 is a medium-severity SQL injection vulnerability found in version 1.0 of the code-projects Currency Exchange System. The flaw exists in the /viewserial.php file, where improper handling of the 'ID' parameter allows remote attackers to inject malicious SQL commands without authentication or user interaction. Exploiting this vulnerability could lead to unauthorized data access or modification, impacting confidentiality, integrity, and availability of the system. Although no public exploits are currently known in the wild, the vulnerability has been publicly disclosed, increasing the risk of exploitation. European organizations using this software, especially financial institutions or currency exchange services, may face data breaches or operational disruptions. Mitigation requires immediate code review and patching to sanitize inputs, implementing parameterized queries, and monitoring for suspicious database activity. Countries with significant financial sectors and higher adoption of this product are at greater risk. Given the ease of remote exploitation and potential data impact, organizations should prioritize remediation to prevent compromise.

Impact

For European organizations, especially those in the financial sector or providing currency exchange services, this vulnerability poses a significant risk. Exploitation could lead to unauthorized disclosure of sensitive financial data, customer information, or transaction records, undermining confidentiality. Integrity could be compromised through unauthorized modification or deletion of data, potentially affecting financial calculations and reporting. Availability might be impacted if attackers execute destructive SQL commands or cause database corruption, leading to service outages. Given the remote and unauthenticated nature of the attack, threat actors could exploit this vulnerability at scale, targeting multiple organizations. This could result in regulatory penalties under GDPR due to data breaches, reputational damage, and financial losses. The medium severity score suggests moderate but non-trivial risk, warranting prompt attention to prevent escalation. Organizations relying on this software without timely patches are particularly vulnerable to targeted attacks or opportunistic exploitation.

Summary

CVE-2025-14216 identifies a SQL injection vulnerability in the code-projects Currency Exchange System version 1.0, specifically in the /viewserial.php endpoint. The vulnerability arises from improper sanitization or validation of the 'ID' parameter, which is directly used in SQL queries. This allows an unauthenticated remote attacker to inject arbitrary SQL code, potentially enabling unauthorized access to sensitive database information, data manipulation, or disruption of service. The vulnerability does not require any user interaction or privileges, making it easier to exploit remotely. The CVSS 4.0 base score is 6.9 (medium), reflecting the network attack vector, low complexity, no authentication, and partial impact on confidentiality, integrity, and availability. Although no exploits are currently reported in the wild, the public disclosure increases the likelihood of future exploitation attempts. The affected product is a currency exchange system, which typically handles sensitive financial data, increasing the risk profile. The lack of available patches or mitigations from the vendor necessitates immediate defensive measures by users. The vulnerability highlights the critical need for secure coding practices such as input validation and 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 15 Dec 2025, 05:03 UTC

Technical details

References

Community reviews

Related threats