CVE-2025-12215
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 |
|---|---|---|
| projectworlds | online_shopping_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?
CVE-2025-12215 is a critical SQL injection vulnerability in Projectworlds Online Shopping System version 1.0, specifically in the /login_submit.php file. The flaw occurs due to improper handling and insufficient validation of the 'keywords' parameter, which allows attackers to inject malicious SQL code into database queries. This can lead to unauthorized access to the database, enabling attackers to view, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data leakage, data tampering, deletion of data, and potentially full system control by attackers. It can also lead to service disruption. Since the exploit can be launched remotely without authentication, it poses a high risk to the confidentiality, integrity, and availability of the affected system. [1, 2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability can negatively affect compliance with standards and regulations such as GDPR and HIPAA because it allows unauthorized access and potential exposure or modification of sensitive personal or protected health information. Such data breaches violate requirements for data confidentiality, integrity, and security mandated by these regulations, potentially leading to legal and financial consequences. [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 /login_submit.php endpoint for SQL injection in the 'keywords' parameter. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://<target>/login_submit.php" --data="keywords=12345&location=&search=search" --method=POST --batch. Additionally, manual testing with payloads such as boolean-based blind SQL injection (e.g., keywords=12345' AND 7943=7943 AND 'Zeqa'='Zeqa) or time-based blind SQL injection (e.g., keywords=12345' RLIKE SLEEP(5) AND 'bMvB'='bMvB) can be used to confirm the vulnerability. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection. 2) Apply strict input validation and filtering on the 'keywords' parameter to ensure only expected input is accepted. 3) Minimize database user privileges by avoiding use of high-privilege accounts for routine database operations. 4) Conduct regular security audits and code reviews to identify and fix vulnerabilities promptly. If possible, replace or update the affected component to a secure version. [1, 2]