CVE-2025-14217
BaseFortify
Publication date: 2025-12-08
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| code-projects | currency_exchange_system | 1.0 |
| fabian | currency_exchange_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access to sensitive database information, data manipulation, and potential full system compromise. Such impacts on confidentiality, integrity, and availability of data can lead to non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data. Exploitation of this SQL injection flaw could result in data breaches and unauthorized disclosure of protected information, thereby violating these regulations. [1, 2, 3]
Can you explain this vulnerability to me?
This vulnerability is a SQL injection in the Currency Exchange System 1.0, specifically in the /edittrns.php file. Manipulating the 'ID' argument in this file allows an attacker to inject malicious SQL code. The attack can be performed remotely, and an exploit is publicly available.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to execute arbitrary SQL commands on the database, potentially leading to unauthorized data access, data modification, or deletion. This can compromise the integrity, confidentiality, and availability of the system's data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the vulnerable parameter 'id' in the /edittrns.php file for injection flaws. Tools like sqlmap can be used to automate detection using payloads such as boolean-based blind, error-based, time-based blind (using SLEEP), and UNION-based SQL injection. Example commands with sqlmap include: sqlmap -u "http://target/edittrns.php?id=1" --batch --dbs to enumerate databases. Additionally, Google dorking with the query inurl:edittrns.php can help identify vulnerable targets on the internet. [1, 2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Rewriting all SQL queries in /edittrns.php to use prepared statements with parameter binding (e.g., mysqli_prepare() or PDO) to prevent SQL injection. 2) Implement strict input validation and filtering to ensure the 'id' parameter is numeric using PHP functions like filter_var() or is_numeric(). 3) Minimize database user privileges by restricting permissions to only what is necessary, avoiding administrative rights. 4) Conduct regular security audits and code reviews to detect and fix vulnerabilities proactively. If possible, replace the affected component with a secure alternative. [2, 3]