Skip to main content
CVE-2025-59939VulnerabilityPublished Updated

CVE-2025-59939: LabRedesCefetRJ WeGIA · SQL Injection

Affects LabRedesCefetRJ WeGIASource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 3.5.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Sep 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 2026-10-25.

What to do

Upgrade LabRedesCefetRJ WeGIA to 3.5.0.

Affected software

ProductAffectedFixed in
LabRedesCefetRJ WeGIAAffected
  • <3.5.0
Fixed in
  • 3.5.0

AI-suggested

European organizations using WeGIA should immediately upgrade to version 3.5.0 or later, where the vulnerability is patched. If immediate upgrade is not feasible, implement web application firewall (WAF) rules to detect and block SQL injection patterns targeting the control.php endpoint and specifically the id_produto parameter. Conduct thorough input validation and sanitization on all user-supplied data, especially parameters that interact with the database. Employ prepared statements and parameterized queries in any custom integrations or extensions of WeGIA. Regularly audit and monitor database logs for suspicious queries or anomalies. Implement strict access controls to limit the privileges of accounts interacting with the database to minimize potential damage. Finally, conduct security awareness training for developers and administrators on secure coding practices to prevent similar vulnerabilities.

Description

WeGIA is a Web manager for charitable institutions. Prior to version 3.5.0, WeGIA is vulnerable to SQL Injection attacks in the control.php endpoint with the following parameters: nomeClasse=ProdutoControle&metodo=excluir&id_produto=[malicious command]. It is necessary to apply prepared statements methods, sanitization, and validations on theid_produto parameter. This issue has been patched in version 3.5.0.

References

Community reviews

Loading reviews…