CVE-2025-15410
BaseFortify
Publication date: 2026-01-01
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 |
|---|---|---|
| anisha | online_guitar_store | 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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not contain information regarding the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.
Can you explain this vulnerability to me?
CVE-2025-15410 is a SQL injection vulnerability in the Online Guitar Store 1.0 project, specifically in the /login.php file. The vulnerability occurs because the L_email parameter is directly used in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This can lead to unauthorized database operations such as data leakage, tampering, or full system compromise. The attack can be performed remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can result in unauthorized access to the database, leakage of sensitive information, data tampering, disruption of services, and potentially full system compromise. Since no authentication is required, attackers can remotely exploit this flaw easily, posing significant risks to system security and business continuity. [1, 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.php endpoint for SQL injection via the L_email parameter. One approach is to use SQL injection testing tools or manual commands such as curl or sqlmap. For example, using sqlmap: sqlmap -u "http://target/login.php" --data="L_email=test'" --risk=3 --level=5 to test for injection. Additionally, attackers may be identified by monitoring for unusual SQL errors or suspicious input patterns in logs. Google dorking with queries like inurl:login.php can help identify vulnerable targets externally. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying input validation and sanitization on the L_email parameter, using prepared statements or parameterized queries to separate SQL code from data, and minimizing database user permissions to reduce impact if exploited. Since the vulnerability is due to unsafe handling of user input in SQL queries, refactoring the code to use secure coding practices is essential. If possible, replacing the affected product with a secure alternative is recommended. Monitoring and restricting access to the vulnerable endpoint can also help reduce risk until a fix is applied. [1]