VulnerabilityPublished 11 Mar 2026Updated 12 Mar 2026

CVE-2026-31894: LabRedesCefetRJ WeGIA · Link Following

Affects LabRedesCefetRJ WeGIASource CVE Database V5

Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 3.6.6 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.6.6

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade WeGIA and labredescefetrj/WeGIA to 3.6.6.

Affected software

Product	Affected	Fixed in
LabRedesCefetRJWeGIA	Affected >=3.6.5 <3.6.6	Fixed in 3.6.6
GitHublabredescefetrj/WeGIA`pkg:github/labredescefetrj/WeGIA`Other threats	Affected <3.6.6	Fixed in 3.6.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

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.

CWE-59Improper Link Resolution Before File Access (Link Following) (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
Architecture and Design · Separation of Privilege
Follow the principle of least privilege when assigning access rights to entities in a software system.
OWASP Cheat Sheets
Authorization (opens in a new tab)
Attack patterns
Symlink Attack (opens in a new tab)
Using Malicious Files (opens in a new tab)
Leverage Executable Code in Non-Executable Files (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Mar 2026, 02:16 UTC

WeaknessesCWE-59

Technical details

References

Community reviews

Related threats