CVE-2025-12287
BaseFortify
Publication date: 2025-10-27
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 |
|---|---|---|
| bdtask | wholesale | to 2025-10-13 (inc) |
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-12287 is an SQL injection vulnerability in the Bdtask Wholesale Inventory Control and Inventory Management System, specifically in the /Admin_dashboard/edit_profile file. The vulnerability arises because the 'first_name' and 'last_name' parameters are not properly sanitized before being used in SQL queries. This allows an authenticated attacker to inject malicious SQL commands remotely, potentially extracting sensitive database information via error messages. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of your system. An attacker with authenticated access can exploit the SQL injection flaw to extract sensitive data, modify database contents, or disrupt system operations. Since the exploit is publicly available and no vendor patch exists, the risk of exploitation is significant. [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 /Admin_dashboard/edit_profile endpoint for SQL injection vulnerabilities in the first_name and last_name parameters. Since the exploit requires authentication, you should perform authenticated requests injecting SQL payloads into these parameters and observe error-based SQL injection responses. Using tools like sqlmap with authentication cookies or manual curl commands to send crafted POST requests with SQL injection payloads in first_name or last_name can help detect the vulnerability. For example, a curl command might be: curl -X POST -d "first_name=' OR '1'='1" -d "last_name=test" -b "auth_cookie=your_auth_cookie" https://target/Admin_dashboard/edit_profile. Monitoring error messages or unusual database responses indicates the presence of the vulnerability. [1, 2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable endpoint to trusted users only, implementing web application firewall (WAF) rules to detect and block SQL injection attempts targeting first_name and last_name parameters, and monitoring logs for suspicious activity. Since no vendor patch or fix is available, consider disabling or restricting the affected functionality if possible. Ultimately, replacing the affected product with a secure alternative is recommended due to the lack of vendor response and public availability of proof-of-concept exploits. [2]