CVE-2025-12292
BaseFortify
Publication date: 2025-10-27
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 |
|---|---|---|
| janobe | point_of_sales | 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?
CVE-2025-12292 is a critical SQL injection vulnerability in the SourceCodester Point of Sales 1.0 application, specifically in the /index.php file. The vulnerability occurs because the 'username' parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without any authentication. The injection can be time-based blind SQL injection, enabling unauthorized database operations such as data leakage, modification, deletion, or even full system compromise. The vulnerability is easy to exploit and has been publicly disclosed with proof-of-concept exploits available. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, exposure of sensitive information, data tampering, deletion of data, and potential full system compromise. It threatens the confidentiality, integrity, and availability of the affected system. Attackers can exploit this remotely without any login, potentially causing service interruptions and business continuity issues. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'username' parameter in the /index.php file for SQL injection flaws. A common approach is to use automated tools like sqlmap targeting the affected URL with the 'username' parameter to check for injection vulnerabilities. For example, a command using sqlmap could be: sqlmap -u "http://target/pos/index.php" --data="username=admin123&password=123213" -p username --dbms=mysql --technique=T --batch. Additionally, manual testing can be done by injecting SQL payloads into the 'username' parameter and observing the response for anomalies or time delays indicative of time-based blind SQL injection. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Apply strict input validation and filtering on the 'username' parameter to ensure it conforms to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts for routine database operations. 4) Conduct regular security audits to detect and fix vulnerabilities promptly. Since no official patches or fixes are available, replacing the affected product with a secure alternative is recommended if immediate remediation is not feasible. [1, 2, 3]