CVE-2025-53091
BaseFortify
Publication date: 2025-06-27
Last updated on: 2025-07-08
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wegia | wegia | to 3.4.0 (exc) |
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 a Time-Based Blind SQL Injection in the almox parameter of the /controle/getProdutosPorAlmox.php endpoint in WeGIA version 3.3.3. It allows an unauthenticated attacker to inject arbitrary SQL queries because the application does not properly sanitize input. The attacker can exploit this remotely without any authentication or user interaction by using time-based techniques like the SLEEP() function to infer data from the database. [1]
How can this vulnerability impact me? :
The impact includes unauthorized access to sensitive data such as user credentials and logs, database enumeration (schemas, tables, users, versions), potential remote code execution depending on database features, and full application compromise if combined with other vulnerabilities. It has a critical severity with a CVSS score of 10.0, indicating high impact on confidentiality, integrity, and availability. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending specially crafted HTTP requests to the /controle/getProdutosPorAlmox.php endpoint with the almox parameter containing time-based SQL injection payloads using the SLEEP() function. Detection involves measuring response delays that indicate successful injection. For example, using curl or similar tools, you can send requests like: curl -i 'http://target/controle/getProdutosPorAlmox.php?almox=1' and curl -i 'http://target/controle/getProdutosPorAlmox.php?almox=1 AND SLEEP(5)' and compare response times. A significant delay in the second request suggests the presence of the vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade the WeGIA Composer package to version 3.4.0 or later, where this vulnerability is fixed. Additionally, restricting access to the vulnerable endpoint, implementing web application firewalls (WAF) to detect and block SQL injection attempts, and applying input validation and sanitization on the almox parameter can help reduce risk until the patch is applied. [1]