Skip to main content
CVE-2025-14217VulnerabilityPublished

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

Affects code-projects Currency Exchange SystemSource CVE Database V5

0

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
code-projects Currency Exchange SystemAffected
  • =1.0
Fixed in–

AI-suggested

1. Immediately audit and sanitize all user inputs in the /edittrns.php file, especially the 'ID' parameter, using strict validation and allowlisting. 2. Refactor the code to use prepared statements or parameterized queries to prevent SQL injection. 3. Conduct a comprehensive code review of the entire application to identify and remediate similar injection flaws. 4. Monitor network traffic and application logs for suspicious SQL queries or unusual activity targeting the vulnerable endpoint. 5. Restrict database user permissions to the minimum necessary to limit the impact of potential exploitation. 6. If possible, isolate the vulnerable system behind a web application firewall (WAF) configured to detect and block SQL injection attempts. 7. Develop and test patches promptly and deploy them in all affected environments. 8. Educate developers and administrators on secure coding practices to prevent future injection vulnerabilities. 9. Implement regular vulnerability scanning and penetration testing focused on injection flaws. 10. Maintain an incident response plan to quickly address any exploitation attempts.

Description

A vulnerability was identified in code-projects Currency Exchange System 1.0. Impacted is an unknown function of the file /edittrns.php. Such manipulation of the argument ID leads to sql injection. The attack may be performed from remote. The exploit is publicly available and might be used.

References

Community reviews

Loading reviews…