# CVE-2026-33135: WeGIA has Reflected Cross-Site Scripting (XSS) in `novo_memorandoo.php` via `sccs` parameter

> Attackers can inject arbitrary JavaScript via the sccs parameter in novo_memorandoo.php, leading to reflected XSS in WeGIA.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-w5rv-5884-w94v

## What is CVE-2026-33135?

CVE-2026-33135 is a critical cross-site scripting vulnerability in Wegia Wegia, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-33135?

It affects 1 product.


Products: Wegia Wegia.

## How do I fix CVE-2026-33135?

No fix has been published for CVE-2026-33135 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33135 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33135 exists.

## Other vulnerabilities in Wegia Wegia

- [CVE-2026-28409](https://insights.sbomify.com/CVE-2026-28409/): WeGIA Vulnerable to Remote Code Execution (RCE) via OS Command Injection (critical 10.0)
- [CVE-2025-58745](https://insights.sbomify.com/CVE-2025-58745/): WeGIA has a bypass for the fix for CVE-2025-22133 - Arbitrary File Upload leads to Remote Code Execution (RCE) (critical 10.0)
- [CVE-2025-58159](https://insights.sbomify.com/CVE-2025-58159/): WeGIA Authenticated Arbitrary File Upload Leading To Remote Code Execution (RCE) (critical 10.0)
- [CVE-2025-55169](https://insights.sbomify.com/CVE-2025-55169/): WeGIA Path Traversal at endpoint 'html/socio/sistema/download_remessa.php' via parameter 'file' (critical 10.0)
- [CVE-2025-53823](https://insights.sbomify.com/CVE-2025-53823/): WeGIA vulnerable to SQL Injection (Blind Time-Based) in `processa_deletar_socio.php` parameter `id_socio` (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33135 and fix it if it is affected.

What it is: CVE-2026-33135 is a critical cross-site scripting vulnerability in Wegia Wegia, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33135 exists.

Affected product: Wegia Wegia. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33135/ (Markdown: https://insights.sbomify.com/CVE-2026-33135/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33135
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33135
- OSV: https://osv.dev/vulnerability/CVE-2026-33135

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33135/
Summaries are generated and may contain mistakes; the official description above is the record.