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-2026-31894: CWE-59: Improper Link Resolution Before File Access ('Link Following') in LabRedesCefetRJ WeGIA

0
Medium
VulnerabilityCVE-2026-31894cvecve-2026-31894cwe-59
Published: Wed Mar 11 2026 (03/11/2026, 19:05:51 UTC)
Source: CVE Database V5
Vendor/Project: LabRedesCefetRJ
Product: WeGIA

Description

CVE-2026-31894 is a medium severity vulnerability in WeGIA version 3. 6. 5, a web manager for charitable institutions. The vulnerability arises from improper handling of symbolic links during extraction and reading of tar. gz archives in the loadBackupDB() function. Specifically, the PharData class extracts archives without validating symbolic links, and subsequent file reading operations do not verify if files are symlinks, leading to potential unauthorized file access or overwriting. This flaw is fixed in version 3. 6. 6. Exploitation requires high privileges but no user interaction or authentication, and no known exploits are currently reported.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/19/2026, 02:16:12 UTC

Technical Analysis

CVE-2026-31894 is an improper link resolution vulnerability (CWE-59) found in WeGIA, a web management application used by charitable institutions. In version 3.6.5, the loadBackupDB() function extracts tar.gz archives using PHP's PharData class to a temporary directory. The extraction process does not validate whether archive members are symbolic links, allowing an attacker to craft malicious archives containing symlinks. After extraction, the application uses glob() and file_get_contents() to read SQL files from the extracted contents, again without verifying if these files are symlinks. This improper handling can lead to directory traversal or arbitrary file read/write operations, potentially allowing an attacker with access to the backup process to overwrite or read sensitive files outside the intended directory. The vulnerability requires the attacker to have high privileges on the system (as indicated by the CVSS vector) but does not require user interaction or authentication. The flaw is addressed in WeGIA version 3.6.6 by adding validation to prevent symbolic link exploitation during archive extraction and file reading. No known exploits are currently reported in the wild, but the vulnerability poses a significant risk due to the sensitive nature of the data managed by WeGIA and the potential for privilege escalation or data compromise.

Potential Impact

The vulnerability could allow an attacker with sufficient privileges to manipulate backup archives to include symbolic links that point to arbitrary files on the server. When these archives are extracted and processed, the attacker could cause the application to overwrite critical files or read sensitive data outside the intended backup scope. This can lead to unauthorized disclosure of confidential information, data integrity violations, or denial of service if critical files are corrupted. Given that WeGIA is used by charitable institutions, the impact includes potential exposure of donor information, financial data, and operational details. The requirement for high privileges limits exploitation to insiders or attackers who have already compromised privileged accounts, but the lack of user interaction or authentication requirements means exploitation can be automated once access is obtained. The medium CVSS score (6.9) reflects the moderate ease of exploitation combined with significant impact on confidentiality and integrity.

Mitigation Recommendations

Organizations should upgrade WeGIA to version 3.6.6 or later, where the vulnerability is patched. Until the upgrade is applied, administrators should restrict access to the backup and restore functions to trusted users only, minimizing the risk of malicious archive uploads. Implement file system monitoring to detect unexpected symbolic links or changes in backup directories. Additionally, consider sandboxing the extraction process or using alternative extraction methods that validate symbolic links and prevent directory traversal. Regularly audit backup files for integrity and unexpected content. Employ strict file permissions on temporary directories used during extraction to limit the impact of any exploitation. Finally, monitor logs for unusual activity related to backup operations that could indicate exploitation attempts.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-09T21:59:02.688Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69b1c2ac2f860ef943697e58

Added to database: 3/11/2026, 7:29:48 PM

Last enriched: 3/19/2026, 2:16:12 AM

Last updated: 4/28/2026, 5:48:55 AM

Views: 74

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 more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses