CVE-2025-15011
BaseFortify
Publication date: 2025-12-22
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 |
|---|---|---|
| carmelo | simple_stock_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-15011 is a SQL injection vulnerability in the Simple Stock System 1.0, specifically in the logout.php file. The vulnerability occurs because the 'uname' parameter is directly used in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This enables unauthorized manipulation of database queries remotely without authentication, potentially leading to unauthorized data access, data tampering, or system control. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to sensitive database information, alteration or tampering of data, full system compromise, and disruption of service availability. Since exploitation requires no authentication and can be done remotely, attackers can easily leverage this flaw to compromise system security and business continuity. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'uname' parameter in the logout.php endpoint for SQL injection. A common approach is to use automated tools like sqlmap to test the injection point, for example: sqlmap -u "http://target/logout.php?uname=123" --batch. Additionally, searching for the vulnerable endpoint using Google dorking with queries like "inurl:logout.php" can help identify potentially affected systems. Monitoring for unusual or unauthorized SQL queries targeting the 'uname' parameter may also indicate exploitation attempts. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'uname' parameter, and limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine operations. These measures help protect system integrity and data security in the Simple Stock System application. [1, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of CVE-2025-15011 on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows unauthorized database access, data extraction, and manipulation, it could potentially lead to breaches of confidentiality and integrity of sensitive data, which are critical concerns under regulations like GDPR and HIPAA. Organizations using the affected software might face compliance risks if this vulnerability is exploited and sensitive personal or health data is compromised. Remediation is necessary to maintain data security and regulatory compliance. [1, 2, 3]