CVE-2025-54079
BaseFortify
Publication date: 2025-07-18
Last updated on: 2025-07-30
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.6 (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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability can negatively affect compliance with standards such as GDPR and HIPAA because it allows unauthorized access to sensitive information, potentially leading to data breaches. Such breaches violate data protection and privacy requirements mandated by these regulations, exposing organizations to legal and financial penalties. [1]
Can you explain this vulnerability to me?
This vulnerability is a critical SQL Injection issue in the WeGIA web manager, specifically in the `idatendido` parameter of the `/html/atendido/Profile_Atendido.php` endpoint in versions prior to 3.4.6. It allows an authorized attacker to inject malicious SQL code, enabling them to execute arbitrary SQL queries on the database. This can lead to unauthorized access to sensitive information, full database compromise, and even Denial of Service through time-delay queries. The vulnerability is exploitable remotely with low complexity and requires only minimal privileges. [1]
How can this vulnerability impact me? :
The impact of this vulnerability includes unauthorized access to sensitive data stored in the database, potential full compromise of the database, and possible Denial of Service attacks caused by time-based SQL injection payloads. This can lead to data breaches, loss of data integrity, and disruption of service 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 crafted GET requests to the endpoint `/html/atendido/Profile_Atendido.php` with malicious payloads in the `idatendido` parameter to test for SQL Injection. For example, a time-based blind SQL injection test can be performed using a payload like `(select*from(select(sleep(20)))a)` which causes a delay in the response if vulnerable. A sample curl command to test this would be: `curl -i 'http://<target>/html/atendido/Profile_Atendido.php?idatendido=(select*from(select(sleep(20)))a)'`. Observing a significant delay in response time indicates the presence of the vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the WeGIA package to version 3.4.6 or later, where the SQL Injection vulnerability in the `idatendido` parameter has been fixed. Until the update can be applied, restrict access to the vulnerable endpoint to authorized users only and consider implementing web application firewall (WAF) rules to block suspicious SQL injection payloads targeting the `idatendido` parameter. [1]