CVE-2026-23722VulnerabilityPublished 16 Jan 2026

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

Affects LabRedesCefetRJ WeGIASource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical : upgrade to 3.6.2 as a priority.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

9.1Critical

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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.2.

Affected software

Product	Affected	Fixed in
LabRedesCefetRJWeGIA	Affected <3.6.2	Fixed in 3.6.2
GitHublabredescefetrj/WeGIA`pkg:github/labredescefetrj/WeGIA`Other threats	Affected <3.6.2	Fixed in 3.6.2

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

AI-suggested

1. Immediately upgrade all WeGIA installations to version 3.6.2 or later, where the vulnerability is patched. 2. Implement strict input validation and output encoding on all user-supplied data, especially parameters reflected in HTML or script contexts. 3. Deploy a robust Content Security Policy (CSP) to restrict the execution of unauthorized scripts and reduce the impact of potential XSS payloads. 4. Conduct regular security audits and code reviews focusing on input handling and output encoding practices. 5. Educate users and administrators about the risks of clicking on suspicious links and encourage the use of security tools such as browser extensions that can detect and block XSS attempts. 6. Monitor web server logs for unusual or suspicious GET requests targeting the id_memorando parameter or similar vectors. 7. Consider implementing Web Application Firewalls (WAFs) with rules designed to detect and block reflected XSS attacks targeting WeGIA. 8. Ensure that session management mechanisms use secure, HttpOnly, and SameSite cookies to mitigate session hijacking risks.

Description

CVE-2026-23722 is a critical reflected Cross-Site Scripting (XSS) vulnerability in the WeGIA web management system for charitable institutions, affecting versions prior to 3.6.2. The flaw exists in the insere_despacho.php script where the id_memorando GET parameter is not properly sanitized or encoded before being reflected in the HTML output. This allows unauthenticated attackers to inject malicious JavaScript, potentially compromising user sessions and data confidentiality and integrity. The vulnerability has a CVSS score of 9.1, indicating high severity, and does not require user interaction or authentication to exploit. Although no known exploits are currently reported in the wild, the vulnerability poses a significant risk to organizations using affected versions of WeGIA. The issue is fixed in version 3.

Impact

For European organizations using WeGIA, this vulnerability poses a significant threat to the confidentiality and integrity of sensitive data managed within the platform, including potentially sensitive information related to charitable activities. Successful exploitation could allow attackers to hijack user sessions, steal credentials, manipulate displayed content, or perform unauthorized actions under the guise of legitimate users. This could lead to reputational damage, data breaches, and regulatory non-compliance, especially under GDPR requirements for protecting personal data. Since WeGIA is used by charitable institutions, exploitation could disrupt critical social services or donor relations. The lack of required authentication and user interaction increases the risk of widespread exploitation if attackers target these organizations. Additionally, the reflected XSS could be used as a vector to deliver further malware or phishing attacks against users. The impact is heightened in environments where WeGIA is integrated with other internal systems or where users have elevated privileges.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/LabRedesCefetRJ/WeGIA/security/advisories/GHSA-g7hh-6qj7-mcqf (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Jan 2026, 20:35 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats