CVE-2021-47777
BaseFortify
Publication date: 2026-01-15
Last updated on: 2026-01-15
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| rib | build_smart_erp | 21.0817 |
Helpful Resources
Exploitability
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an unauthenticated SQL injection in the 'eidValue' parameter of the login validation endpoint in Build Smart ERP version 21.0817. Attackers can send specially crafted SQL queries, including stacked queries like ';WAITFOR DELAY '0:0:3'--, to manipulate the backend Microsoft SQL Server database. This allows execution of arbitrary SQL commands without needing to authenticate, potentially enabling attackers to extract, modify, or disrupt database information. [1]
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized data leakage, modification of database contents, or denial of service by executing arbitrary SQL commands on the backend database. Since it is unauthenticated, attackers do not need valid credentials to exploit it, increasing the risk of compromise and potential disruption of business operations. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted POST requests to the `/acc/validateLogin.asp` endpoint targeting the `eidValue` parameter with SQL injection payloads such as `';WAITFOR DELAY '0:0:3'--`. Monitoring for unusual delays in response times or error messages can indicate successful injection. A sample detection command using curl would be: curl -X POST https://<target>/acc/validateLogin.asp -d "VersionNumber=1&activexVersion=1&XLImportCab=1&updaterActivexVersion=1&lang=en&rptlang=en&loginID=test&userPwd=test&EID=1&eidValue=';WAITFOR DELAY '0:0:3'--&[email protected]" If the response is delayed by approximately 3 seconds, it suggests the presence of the SQL injection vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable endpoint, implementing input validation and parameterized queries to prevent SQL injection, and monitoring logs for suspicious activity. Applying any available patches or updates from the vendor is recommended. If patches are not available, consider deploying web application firewalls (WAF) rules to block malicious payloads targeting the `eidValue` parameter. [1]