Skip to main content
VulnerabilityPublished

CVE-2026-33135: LabRedesCefetRJ WeGIA · Cross-site Scripting

Affects LabRedesCefetRJ WeGIASource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 3.6.7 as a priority.

Data as of 1 Nov 2026, 08:20 UTC

CVSS 3.1 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.6.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 31 Oct 2026.

What to do

Upgrade WeGIA and labredescefetrj/WeGIA to 3.6.7.

Affected software

ProductAffectedFixed in
LabRedesCefetRJWeGIAAffected
  • <3.6.7
Fixed in
  • 3.6.7
GitHublabredescefetrj/WeGIApkg:github/labredescefetrj/WeGIAOther threatsAffected
  • <3.6.7
Fixed in
  • 3.6.7

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

AI-suggested

  1. Upgrade WeGIA to version 3.6.7 or later immediately to apply the official patch that fixes the XSS vulnerability.
  2. Implement strict input validation on all user-supplied data, especially GET parameters, to reject or sanitize unexpected characters.
  3. Apply proper output encoding (e.g., HTML entity encoding) when reflecting user input in HTML contexts to prevent script injection.
  4. Employ Content Security Policy (CSP) headers to restrict execution of unauthorized scripts and reduce impact of XSS attacks.
  5. Conduct regular security code reviews and penetration testing focusing on input handling and output encoding.
  6. Educate users and staff about the risks of clicking untrusted links, especially those containing suspicious URL parameters.
  7. Monitor web server logs for unusual or suspicious requests targeting the novo_memorandoo.php endpoint with 'msg=success' and unusual 'sccs' parameter values.
  8. Consider implementing Web Application Firewalls (WAFs) with rules to detect and block reflected XSS attack patterns targeting this endpoint.

Description

WeGIA is a web manager for charitable institutions. Versions 3.6.6 and below have a Reflected Cross-Site Scripting (XSS) vulnerability in the novo_memorandoo.php endpoint. An attacker can inject arbitrary JavaScript into the sccs GET parameter, which is directly echoed into the HTML response without any sanitization or encoding. The script /html/memorando/novo_memorandoo.php reads HTTP GET parameters to display dynamic success messages to the user. At approximately line 273, the code checks if $_GET['msg'] equals 'success'. If true, it directly concatenates $_GET['sccs'] into an HTML alert <div> and outputs it to the browser. This issue has been fixed in version 3.6.7.

References

Community reviews

Loading reviews…