# CVE-2025-22613: WeGIA Cross-Site Scripting (XSS) Stored endpoint 'informacao_adicional.php' parameter 'descricao'

> Attackers can inject malicious scripts into the WeGIA application via the 'descricao' parameter, leading to stored XSS that executes in victims' browsers.

- **Severity:** Medium 6.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:H/SI:H/SA:H`)
- **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:** 13 Jan 2025
- **Updated:** 14 Jan 2025
- **Also known as:** GHSA-fhpx-54ch-ccxh

## What is CVE-2025-22613?

CVE-2025-22613 is a medium-severity cross-site scripting vulnerability in Wegia Wegia, published on 13 Jan 2025. 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 an open source web manager with a focus on the Portuguese language and charitable institutions. A Stored Cross-Site Scripting (XSS) vulnerability was identified in the `informacao_adicional.php` endpoint of the WeGIA application. This vulnerability allows attackers to inject malicious scripts into the `descricao` parameter. The injected scripts are stored on the server and executed automatically whenever the affected page is accessed by users, posing a significant security risk. The application fails to properly validate and sanitize user inputs in the `informacao_adicional.php` parameter. This lack of validation allows attackers to inject malicious scripts, which are then stored on the server. Whenever the affected page is accessed, the malicious payload is executed in the victim's browser, potentially compromising the user's data and system. This issue has been addressed in version 3.2.6 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

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

## Which versions are affected by CVE-2025-22613?

It affects 1 product.


Products: Wegia Wegia.

## How do I fix CVE-2025-22613?

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

## Is CVE-2025-22613 being exploited?

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

What it is: CVE-2025-22613 is a medium-severity cross-site scripting vulnerability in Wegia Wegia, published on 13 Jan 2025. 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-2025-22613 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-2025-22613/ (Markdown: https://insights.sbomify.com/CVE-2025-22613/index.md)
```

## Sources

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

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