CVE-2025-14216
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 /viewserial.php file. It involves SQL injection caused by manipulation of the ID argument, allowing an attacker to execute unauthorized SQL commands remotely.
How can this vulnerability impact me? :
The vulnerability can allow remote attackers to perform SQL injection, potentially leading to unauthorized access, data leakage, data modification, or disruption of the system's normal operation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this SQL injection vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows unauthorized access, theft, tampering, or destruction of sensitive data, it could potentially lead to non-compliance with data protection regulations that require safeguarding personal and sensitive information. Organizations using the affected software may face risks related to confidentiality and integrity of data, which are critical aspects of such regulations. [1, 2, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability in /viewserial.php can be detected by testing the 'id' parameter for SQL injection flaws. Tools like sqlmap can be used to automate detection with commands such as: sqlmap -u "http://target/viewserial.php?id=1" --batch. Additionally, manual testing can include injecting payloads like '1' OR NOT 5995=5995#' or time-based payloads like '1' AND (SELECT SLEEP(5))-- to observe abnormal behavior or delays. Google Dorking can also help identify vulnerable targets by searching for URLs containing 'inurl:viewserial.php'. [1, 2, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Rewriting all SQL queries in /viewserial.php and other affected files to use prepared statements with parameter binding (e.g., mysqli_prepare() or PDO) to prevent SQL injection. 2) Implement strict input validation and filtering, ensuring parameters like 'id' are numeric using PHP functions such as filter_var() or is_numeric(). 3) Minimize database user permissions by restricting the database user to only necessary privileges, avoiding administrative rights like DROP or ALTER. 4) Conduct regular security audits and code reviews to proactively detect and fix vulnerabilities. If possible, consider replacing the affected software with an alternative product. [2, 4, 1]