Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-62177: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in LabRedesCefetRJ WeGIA

0
High
VulnerabilityCVE-2025-62177cvecve-2025-62177cwe-89
Published: Mon Oct 13 2025 (10/13/2025, 21:09:29 UTC)
Source: CVE Database V5
Vendor/Project: LabRedesCefetRJ
Product: WeGIA

Description

WeGIA is an open source Web Manager for Institutions with a focus on Portuguese language users. Prior to 3.5.1, a SQL Injection vulnerability was identified in the /html/funcionario/dependente_listar.php endpoint, specifically in the id_funcionario parameter. This vulnerability allows attackers to execute arbitrary SQL commands, compromising the confidentiality, integrity, and availability of the database. This vulnerability is fixed in 3.5.1.

AI-Powered Analysis

AILast updated: 10/13/2025, 21:34:18 UTC

Technical Analysis

CVE-2025-62177 is a SQL Injection vulnerability classified under CWE-89 found in the WeGIA web management system developed by LabRedesCefetRJ. The vulnerability specifically targets the id_funcionario parameter in the /html/funcionario/dependente_listar.php endpoint. Prior to version 3.5.1, this parameter is improperly sanitized, allowing attackers to inject malicious SQL code. Exploitation can be performed remotely over the network without user interaction but requires high privileges, likely meaning an authenticated user with elevated rights. Successful exploitation enables attackers to execute arbitrary SQL commands, potentially leading to unauthorized data disclosure, data modification, or deletion, and disruption of service. The vulnerability affects all versions before 3.5.1, which was released to address this issue. The CVSS 4.0 vector indicates a network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:H interpreted as high privileges needed), no user interaction (UI:N), and high impact on confidentiality, integrity, and availability (C:H/I:H/A:H). No known exploits have been reported in the wild yet, but the vulnerability's characteristics make it a significant risk for affected deployments. WeGIA is primarily used by Portuguese language institutions, which suggests a regional focus but does not exclude other users. The vulnerability's exploitation could lead to severe data breaches and operational disruptions in affected organizations.

Potential Impact

For European organizations, especially those with Portuguese language ties or institutions using WeGIA, this vulnerability poses a significant risk. Exploitation could lead to unauthorized access to sensitive institutional data, including personal information of employees or dependents managed via the system. Data integrity could be compromised, allowing attackers to alter records, potentially affecting institutional operations and trustworthiness. Availability impacts could disrupt critical administrative functions, causing operational downtime. Given the high CVSS score and the nature of the vulnerability, attackers could leverage this flaw to escalate privileges or move laterally within networks. The risk is heightened for organizations that have not yet upgraded to WeGIA 3.5.1 or implemented compensating controls. The lack of known exploits in the wild does not diminish the potential impact, as the vulnerability is straightforward to exploit with network access and appropriate privileges. European institutions in education, government, or public administration using WeGIA are particularly vulnerable to data breaches and service disruptions.

Mitigation Recommendations

The primary mitigation is to upgrade WeGIA installations to version 3.5.1 or later, where the vulnerability has been fixed. Organizations should immediately audit their WeGIA deployments to identify affected versions. In addition to patching, implement strict input validation and use parameterized queries or prepared statements to prevent SQL injection. Restrict access to the vulnerable endpoint by enforcing strong authentication and authorization controls, limiting high-privilege user accounts. Monitor logs for unusual database queries or access patterns that may indicate exploitation attempts. Employ web application firewalls (WAFs) with rules designed to detect and block SQL injection payloads targeting the id_funcionario parameter. Conduct regular security assessments and penetration tests focused on injection vulnerabilities. Finally, ensure backups of critical data are maintained and tested for recovery to mitigate availability impacts in case of an attack.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-10-07T16:12:03.426Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68ed6d2e38344d8bcf324869

Added to database: 10/13/2025, 9:20:46 PM

Last enriched: 10/13/2025, 9:34:18 PM

Last updated: 10/14/2025, 7:48:25 PM

Views: 28

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats