CVE-2025-14218VulnerabilityPublished 8 Dec 2025

CVE-2025-14218: 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 and review the /editotheraccount.php code to identify and fix the input validation flaw on the ID parameter. 2. Implement parameterized queries or prepared statements to prevent SQL injection attacks. 3. Apply strict input validation and sanitization for all user-supplied data, especially parameters used in SQL queries. 4. 5. Employ web application firewalls (WAFs) with SQL injection detection and prevention rules tailored to the application’s traffic patterns. 6. Conduct regular security testing, including automated scanning and manual penetration testing focused on injection flaws. 7. Monitor logs for suspicious database queries or unusual application behavior indicative of exploitation attempts. 8. Educate developers on secure coding practices to prevent similar vulnerabilities in future releases.

Description

A security flaw has been discovered in code-projects Currency Exchange System 1.0. The affected element is an unknown function of the file /editotheraccount.php. Performing manipulation of the argument ID results in sql injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may be exploited.

Impact

For European organizations, especially those in the financial sector or operating currency exchange platforms using the affected software, this vulnerability poses a significant risk. Exploitation could lead to unauthorized disclosure of sensitive customer and transactional data, undermining confidentiality. Attackers could also alter or delete data, impacting data integrity and potentially causing financial discrepancies or fraud. Availability could be affected if attackers execute destructive SQL commands or cause database corruption, leading to service outages. Regulatory compliance risks are heightened under GDPR due to potential data breaches. The medium severity score suggests a moderate but tangible threat, particularly given the public availability of an exploit. Organizations relying on this system may face reputational damage, financial loss, and legal consequences if the vulnerability is exploited.

Summary

CVE-2025-14218 is an SQL injection vulnerability identified in the code-projects Currency Exchange System version 1.0. The vulnerability resides in an unspecified function within the /editotheraccount.php file, where the ID parameter is improperly sanitized, allowing attackers to inject malicious SQL code. This flaw can be exploited remotely without requiring authentication or user interaction, making it highly accessible to attackers. The injection can lead to unauthorized data access, modification, or deletion within the backend database, potentially exposing sensitive financial information or disrupting system operations. The CVSS 4.0 score of 6.9 reflects a medium severity, considering the vulnerability's remote exploitability and impact on confidentiality, integrity, and availability, albeit with limited scope and no privilege requirements. Although no active exploits have been observed in the wild, the public release of an exploit increases the urgency for affected parties to implement mitigations. The vulnerability highlights the critical need for secure coding practices such as input validation and the use of parameterized queries in web applications handling financial data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Dec 2025, 06:02 UTC

Technical details

References

Community reviews

Related threats