
Security advisory documenting CVE-2026-31158, an unauthenticated boolean-based SQL injection in a CRM login form's TxtUsername parameter, with reproduction steps and mitigations.
A Boolean-based SQL Injection vulnerability was reported in the login functionality of a CRM web application hosted at crm.softtradeindia.com. Improper handling of user-supplied input in the TxtUsername parameter may allow an attacker to manipulate backend SQL query logic and potentially bypass authentication controls.
Scope of impact: The reported vulnerability affects the application's login functionality. If authentication bypass is confirmed, a remote attacker without valid credentials may gain unauthorized access to protected application functionality. The actual impact depends on the backend implementation, database permissions, and authorization controls.
TxtUsernameThe vulnerability was reported in the login functionality, where the TxtUsername parameter processes user-supplied input.
If the application incorporates this input into a dynamically constructed SQL query without proper parameterization, specially crafted input may alter the intended query logic.
Boolean-based SQL Injection involves influencing SQL conditions and observing application behavior to determine whether user input affects the backend query.
The underlying SQL statement, database engine, and exact implementation details have not been independently confirmed.
The vulnerability was reported in the login page:
http://crm.softtradeindia.com/
Reproduction overview:
TxtUsername parameter.Expected behavior: The application should reject invalid credentials and treat user-supplied input strictly as data.
Reported behavior: The login functionality was reported to be susceptible to Boolean-based SQL Injection, potentially allowing authentication bypass.
Note: Include a specific test payload and observed response only after verifying the result and ensuring the evidence contains no credentials, session tokens, or other sensitive information.
Successful exploitation may allow an unauthenticated attacker to bypass authentication controls and access protected application functionality.
Potential consequences include:
The actual impact depends on the application's backend implementation, database permissions, and access-control mechanisms. Remote code execution has not been independently established.
Use the following measures to address the reported vulnerability:
YYYY-MM-DD — Vulnerability discoveredYYYY-MM-DD — Reported to the vendor2026-01-19 — CVE request date2026-04-04 — CVE ID assign2026-10-23 — Public disclosureDiscovered and reported by Kavar Hardik.
This advisory is intended for vulnerability documentation, authorized security research, and remediation awareness.