Skip to main content
VulnerabilityPublished Updated

CVE-2025-58159: LabRedesCefetRJ WeGIA · Unrestricted File Upload

Affects LabRedesCefetRJ WeGIASource CVE Database V5

0

Mentioned vulnerabilities

Not known to be exploited · CVSS 10.0 Critical : upgrade to 3.4.11 as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.4.11
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade LabRedesCefetRJ WeGIA to 3.4.11.

Affected software

ProductAffectedFixed in
LabRedesCefetRJ WeGIAAffected
  • <3.4.11
Fixed in
  • 3.4.11

AI-suggested

  1. Immediate upgrade to WeGIA version 3.4.11 or later, where the vulnerability is patched, is the most effective mitigation.
  2. Implement strict file upload validation controls: enforce whitelisting of allowed file types/extensions, reject files with executable extensions such as .php, and verify MIME types server-side.
  3. Employ server-side sanitization of uploaded filenames to remove or neutralize dangerous characters and extensions.
  4. Configure web server settings to prevent execution of uploaded files in directories used for file uploads, e.g., disable PHP execution in upload folders via .htaccess or equivalent.
  5. Monitor web server logs for suspicious upload activity or execution attempts of unexpected file types.
  6. Conduct regular security audits and penetration testing focusing on file upload functionalities.
  7. Educate administrators and developers on secure coding practices related to file handling to prevent recurrence.
  8. If immediate upgrade is not feasible, consider temporary mitigations such as restricting upload permissions to trusted users only and isolating the application environment.

Description

WeGIA is a Web manager for charitable institutions. Prior to version 3.4.11, a remote code execution vulnerability was identified, caused by improper validation of uploaded files. The application allows an attacker to upload files with arbitrary filenames, including those with a .php extension. Because the uploaded file is written directly to disk without adequate sanitization or extension restrictions, a spreadsheet file followed by PHP code can be uploaded and executed on the server, leading to arbitrary code execution. This is due to insufficient mitigation of CVE-2025-22133. This issue has been patched in version 3.4.11.

References

Community reviews

Loading reviews…