# CVE-2026-61719: WeGIA: Stored Cross-Site Scripting (XSS) in "historico_prontuarios.php" via "textoProntuario" Field


- **Severity:** High 8.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026

## What is CVE-2026-61719?

CVE-2026-61719 is a high-severity vulnerability in LabRedesCefetRJ WeGIA, published on 29 Oct 2026. 

### Official description

WeGIA is a web manager for charitable institutions. Prior to 3.8.7, a stored cross-site scripting vulnerability in `saude/historico_prontuarios.php` arises because the `textoProntuario` field accepts arbitrary HTML or JavaScript without proper sanitization. An attacker able to create or access a patient's medical record can submit the field through `POST /controle/control.php` with `nomeClasse=SaudeControle`, `metodo=alterarProntuario`, and `id_fichamedica`. The stored content is rendered when another user accesses `/html/saude/historico_prontuarios.php` with `id_historico`, automatically executing attacker-controlled JavaScript in the victim's browser. The vulnerability permits session cookie theft and potential account compromise depending on the victim's privileges. This issue is fixed in version 3.8.7.

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

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


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

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

## Is CVE-2026-61719 being exploited?

There is no known exploitation of CVE-2026-61719 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61719 is a high-severity vulnerability in LabRedesCefetRJ WeGIA, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-61719 in the wild and no public exploit code.

Affected product: LabRedesCefetRJ 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-61719/ (Markdown: https://insights.sbomify.com/CVE-2026-61719/index.md)
```

## Sources

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

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