CVE-2025-10426
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-15

Last updated on: 2026-04-29

Assigner: VulDB

Description
A security flaw has been discovered in itsourcecode Online Laundry Management System 1.0. This affects an unknown function of the file /login.php. Performing manipulation of the argument Username results in sql injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may be exploited.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-15
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2025-09-15
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
campcodes online_laundry_management_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
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.
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.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-10426 is a critical SQL injection vulnerability in the itsourcecode Online Laundry Management System version 1.0, specifically in the /login.php file. The vulnerability occurs because the 'username' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This flaw enables unauthorized access to the database, potentially leading to data leakage, modification, deletion, or full system compromise. The attack can be performed remotely without authentication, making it easy to exploit. [1, 3]


How can this vulnerability impact me? :

This vulnerability can severely impact you by allowing attackers to remotely execute arbitrary SQL commands on your database without authentication. This can lead to unauthorized access, exposure of sensitive information, data modification or deletion, and potential disruption of services. The flaw compromises the confidentiality, integrity, and availability of your system, posing a serious threat to business continuity and security. [1, 2, 3]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This SQL injection vulnerability can be detected by testing the /login.php endpoint with specially crafted payloads targeting the 'username' parameter. Tools like sqlmap can be used to automate detection and exploitation attempts. Example payloads include boolean-based blind SQL injection (e.g., username=admin' AND 1=1 -- ), error-based, and time-based blind SQL injection payloads as demonstrated in the proof-of-concept. A sample sqlmap command to test the vulnerability is: sqlmap -u "http://target/login.php" --data="username=admin&password=any" --risk=3 --level=5 --batch. Additionally, Google Dorking such as searching for inurl:login.php can help identify potentially vulnerable targets. [1, 3]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include: 1) Replacing or updating the affected Online Laundry Management System component if a fixed version is available. 2) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 3) Applying strict input validation and sanitization on the 'username' parameter to ensure only expected input formats are accepted. 4) Minimizing database user privileges to reduce impact if exploited. 5) Conducting regular security audits to detect and remediate vulnerabilities promptly. Since no known countermeasures are currently identified, replacing the affected product or component is strongly recommended. [1, 3, 2]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart