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

0
Critical
VulnerabilityCVE-2025-62360cvecve-2025-62360cwe-89
Published: Mon Oct 13 2025 (10/13/2025, 21:24:48 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_documento.php endpoint, specifically in the id_dependente 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/21/2025, 00:38:53 UTC

Technical Analysis

CVE-2025-62360 is a critical SQL Injection vulnerability identified in the WeGIA web management system developed by LabRedesCefetRJ, targeting institutions primarily using Portuguese language software. The vulnerability resides in the id_dependente parameter of the /html/funcionario/dependente_documento.php endpoint in versions prior to 3.5.1. Improper neutralization of special elements in this parameter allows attackers to inject malicious SQL commands directly into the backend database query. This can lead to unauthorized data access, modification, or deletion, severely impacting the confidentiality, integrity, and availability of the database. The vulnerability is exploitable remotely without user interaction but requires high privileges, indicating that an attacker must have some level of authenticated access to exploit it. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H) reflects network attack vector, low attack complexity, no user interaction, but requiring high privileges and causing high impact across confidentiality, integrity, and availability. Although no public exploits are currently reported, the critical nature and ease of exploitation make it a significant threat. The issue was resolved in WeGIA version 3.5.1, which properly sanitizes the id_dependente parameter to prevent SQL injection. Organizations using affected versions should upgrade immediately and review their database access controls and monitoring.

Potential Impact

For European organizations, especially those in Portugal and countries with Portuguese-speaking populations, this vulnerability poses a severe risk. Exploitation could lead to unauthorized disclosure of sensitive institutional data, including personnel records and dependent documentation, potentially violating GDPR and other data protection regulations. Integrity of data could be compromised, leading to misinformation or operational disruption. Availability could also be affected if attackers execute destructive SQL commands or cause database corruption, resulting in downtime and loss of service continuity. The requirement for high privileges to exploit somewhat limits the attack surface but does not eliminate risk, as insider threats or compromised accounts could be leveraged. The critical CVSS score underscores the potential for significant operational and reputational damage. Given the institutional focus of WeGIA, attacks could disrupt educational or governmental services, amplifying the impact within Europe.

Mitigation Recommendations

1. Immediate upgrade to WeGIA version 3.5.1 or later, where the vulnerability is patched. 2. Conduct a thorough audit of user privileges to ensure that only necessary personnel have high-level access, minimizing the risk of privilege abuse. 3. Implement strict input validation and parameterized queries if custom modifications or integrations exist beyond the vendor patch. 4. Deploy Web Application Firewalls (WAFs) configured to detect and block SQL injection attempts targeting the id_dependente parameter and related endpoints. 5. Monitor database logs and application logs for unusual query patterns or failed injection attempts. 6. Conduct regular security assessments and penetration testing focused on injection flaws. 7. Educate administrators and developers on secure coding practices and the importance of timely patching. 8. Consider network segmentation to isolate critical database servers from less trusted network zones. 9. Prepare incident response plans specifically addressing potential SQL injection exploitation scenarios.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-10-10T14:22:48.202Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68ed702cefcc33289f469154

Added to database: 10/13/2025, 9:33:32 PM

Last enriched: 10/21/2025, 12:38:53 AM

Last updated: 12/2/2025, 10:48:00 PM

Views: 118

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