CVE-2025-14218
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
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 /editotheraccount.php file for SQL injection flaws. Tools like sqlmap can be used to automate detection with commands such as: sqlmap -u "http://target/editotheraccount.php?id=1" --batch --dbs. Additionally, manual testing can include injecting payloads like 'id=-4946' OR 1734=1734#' to observe SQL behavior changes. Google dorking with the query inurl:editotheraccount.php can help identify vulnerable targets on the network or internet. [1, 2, 3]
Can you explain this vulnerability to me?
This vulnerability is a SQL injection flaw in the Currency Exchange System 1.0, specifically in an unknown function within the file /editotheraccount.php. By manipulating the argument ID, an attacker can 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 unauthorized SQL commands on the database, potentially leading to data leakage, data modification, or disruption of service. Since it can be exploited remotely without authentication, it poses a significant risk to the confidentiality, integrity, and availability of the affected system.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Rewriting all SQL queries in /editotheraccount.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 strictly numeric using PHP functions like filter_var() or is_numeric(). 3) Restrict database user permissions to the minimum necessary, avoiding administrative rights such as DROP or ALTER. 4) Conduct regular security audits and code reviews to proactively detect and fix vulnerabilities. [1, 3]