# CVE-2026-35399: WeGIA has Stored XSS in backup file names

> Attackers can inject malicious scripts via backup filenames in WeGIA, leading to session hijacking or unauthorized actions in victim browsers.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA: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:** 6 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-fmwv-62wf-2hgx

## What is CVE-2026-35399?

CVE-2026-35399 is a high-severity cross-site scripting vulnerability in Wegia Wegia, published on 6 Apr 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. Prior to 3.6.9, a stored XSS vulnerability allows an attacker to inject malicious scripts through a backup filename. This could lead to unauthorized execution of malicious code in the victim's browser, compromising session data or executing actions on behalf of the user. This vulnerability is fixed in 3.6.9.

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

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

It affects 1 product.


Products: Wegia Wegia.

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

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

## Is CVE-2026-35399 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35399 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-35399 and fix it if it is affected.

What it is: CVE-2026-35399 is a high-severity cross-site scripting vulnerability in Wegia Wegia, published on 6 Apr 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-35399 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-35399/ (Markdown: https://insights.sbomify.com/CVE-2026-35399/index.md)
```

## Sources

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

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