CVE-2025-14215
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
Can you explain this vulnerability to me?
This vulnerability exists in the Currency Exchange System 1.0, specifically in the /edit.php file. It is caused by improper handling of the 'ID' argument, which allows an attacker to perform SQL injection. This means an attacker can manipulate the database queries remotely by injecting malicious SQL code through the ID parameter.
How can this vulnerability impact me? :
The vulnerability can allow a remote 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 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 can lead to breaches of confidentiality, integrity, and availability of data, which are critical requirements under common standards and regulations like GDPR and HIPAA. Therefore, exploitation of this SQL injection vulnerability could result in non-compliance with these regulations due to unauthorized data exposure and potential data loss or tampering. [1, 2, 4]
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 'id' parameter in the /edit.php file for injection flaws. Tools like sqlmap can be used to automate detection. Example commands include: - Boolean-based blind injection test: curl "http://target/edit.php?id=-3347' OR 4988=4988#" - Error-based injection test: curl "http://target/edit.php?id=1' OR (SELECT 6462 FROM(SELECT COUNT(*),CONCAT(0x7170626a71,(SELECT (ELT(6462=6462,1))),0x71787a6271,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)--" - Time-based blind injection test: curl "http://target/edit.php?id=1' AND (SELECT 2645 FROM (SELECT(SLEEP(5)))yaLb)--" Additionally, attackers can identify vulnerable targets using Google dorking with queries like "inurl:edit.php" to find instances of the vulnerable application. Using sqlmap with the URL and parameter can automate detection and exploitation confirmation. [1, 2, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Use prepared statements with parameter binding (e.g., mysqli_prepare() or PDO) in the /edit.php file to separate SQL code from user input and prevent injection. 2. Implement strict input validation and filtering, ensuring 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 such as DROP or ALTER. 4. Conduct regular security audits and code reviews to proactively detect and fix vulnerabilities. If immediate code changes are not possible, consider restricting access to the vulnerable endpoint or replacing the affected product with a secure alternative. [2, 4]