CVE-2026-33136

WeGIA is a web manager for charitable institutions.

Verified by Precogs Threat Research
Last Updated: Mar 20, 2026
Base Score
9.3CRITICAL

Executive Summary

CVE-2026-33136 is a critical severity vulnerability affecting appsec. It is classified as Cross-Site Scripting (XSS). Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"Precogs AI Analysis Engine identifies web application vulnerabilities through semantic code analysis, detecting injection flaws, broken authentication, and insecure data flows across your entire codebase."

Exploit Probability
High (84%)
Public POC
Available
Exploit Probability
High (84%)
Public POC
Available
Affected Assets
appsecCWE-79

What is this vulnerability?

CVE-2026-33136 is categorized as a critical Cross-Site Scripting (XSS) flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

WeGIA is a web manager for charitable institutions. Versions 3.6.6 and below have a Reflected Cross-Site Scripting (XSS) vulnerability in the listar_memora...

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score9.3 (CRITICAL)
Vector StringCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
PublishedMarch 20, 2026
Last ModifiedMarch 20, 2026
Related CWEsCWE-79

Impact on Systems

Session Hijacking: Attackers can steal active user session tokens (cookies) to impersonate the victim.

Phishing Execution: Malicious scripts can dynamically alter DOM content to present fraudulent login forms.

Worm Propagation: Stored XSS can spread autonomously as users visit the infected page.

How to fix this issue?

Implement the following strategic mitigations immediately to eliminate the attack surface.

1. Output Encoding Implement strict context-aware output encoding (HTML, JavaScript, Attribute, CSS) before rendering user data.

2. Content Security Policy (CSP) Deploy a rigorous CSP header to restrict script execution exclusively to trusted domains.

3. Framework Defenses Utilize native UI framework protections (e.g., React DOM escaping) and avoid dangerouslySetInnerHTML.

Vulnerability Signature

// Example DOM-based XSS vulnerability
const user_input = new URLSearchParams(window.location.search).get('q');
// VULNERABLE: Direct insertion into innerHTML
document.getElementById('results').innerHTML = "Results for: " + user_input; 

// EXPLOIT PAYLOAD: ?q=\<img src=x onerror=alert(document.cookie)\>

References and Sources

Related Vulnerabilitiesvia CWE-79