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-62179: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in LabRedesCefetRJ WeGIA

0
High
VulnerabilityCVE-2025-62179cvecve-2025-62179cwe-89
Published: Mon Oct 13 2025 (10/13/2025, 21:13:59 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/cadastro_funcionario_pessoa_existente.php endpoint, specifically in the cpf 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:04 UTC

Technical Analysis

CVE-2025-62179 is an SQL Injection vulnerability identified in the WeGIA open-source Web Manager, primarily used by Portuguese language institutions. The vulnerability resides in the cpf parameter of the /html/funcionario/cadastro_funcionario_pessoa_existente.php endpoint in versions before 3.5.1. SQL Injection occurs due to improper neutralization of special elements in SQL commands (CWE-89), allowing attackers to inject malicious SQL code. Successful exploitation enables attackers to execute arbitrary SQL queries, potentially leading to unauthorized data disclosure, data manipulation, or deletion, and disruption of database availability. The CVSS 4.0 score of 8.6 reflects a high severity, with an attack vector of network (AV:N), low attack complexity (AC:L), no user interaction (UI:N), but requiring high privileges (PR:H). The vulnerability impacts confidentiality, integrity, and availability at a high level. Although no known exploits are reported in the wild, the risk remains significant due to the nature of SQL Injection attacks. The vulnerability is patched in WeGIA version 3.5.1, and users are strongly advised to upgrade. Given WeGIA’s focus on Portuguese-speaking institutions, the vulnerability primarily affects organizations in regions with Portuguese language prevalence. The lack of authentication bypass means attackers must have high privileges, which somewhat limits exploitation but does not eliminate risk, especially from insider threats or compromised accounts.

Potential Impact

For European organizations, the impact of CVE-2025-62179 can be severe, particularly for institutions using WeGIA for managing sensitive institutional data. Exploitation could lead to unauthorized access to confidential personal data, manipulation or deletion of records, and potential service outages affecting operational continuity. This could result in regulatory non-compliance, especially under GDPR, leading to financial penalties and reputational damage. The high severity and network accessibility mean attackers can remotely exploit the flaw if they have high-level credentials, increasing risk from insider threats or credential theft. The availability of the system could be compromised, impacting critical institutional functions. Additionally, data integrity issues could undermine trust in institutional records. European organizations with Portuguese-speaking user bases or partnerships are at elevated risk due to the product’s target audience. The absence of known exploits in the wild currently reduces immediate risk but does not preclude future exploitation attempts.

Mitigation Recommendations

1. Immediate upgrade to WeGIA version 3.5.1 or later, where the vulnerability is patched, is the most effective mitigation. 2. Restrict access to the vulnerable endpoint (/html/funcionario/cadastro_funcionario_pessoa_existente.php) using network segmentation and firewall rules to limit exposure only to trusted users. 3. Implement strong authentication and access controls to minimize the number of users with high privileges required to exploit the vulnerability. 4. Conduct regular audits of database queries and logs to detect anomalous activities indicative of SQL Injection attempts. 5. Employ Web Application Firewalls (WAFs) with rules specifically designed to detect and block SQL Injection payloads targeting the cpf parameter. 6. Educate administrators and developers on secure coding practices to prevent similar injection flaws. 7. Monitor vendor advisories for any updates or exploit disclosures related to this CVE. 8. If patching is delayed, consider temporary input validation or parameterized query workarounds to reduce injection risk. 9. Perform penetration testing focused on SQL Injection vectors to verify the effectiveness of mitigations.

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: 68ed6d2e38344d8bcf324872

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

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

Last updated: 10/14/2025, 7:49:13 PM

Views: 18

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