# CVE-2025-13221: Intelbras UnniTI usuarios.xml credentials storage

> Attackers can remotely access stored credentials in usuarios.xml, leading to potential account takeover and data exposure.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Nov 2025
- **Updated:** 7 Jan 2026
- **Also known as:** GHSA-f985-hh3h-wcqc

## What is CVE-2025-13221?

CVE-2025-13221 is a medium-severity vulnerability in Intelbras UnniTI, published on 15 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weakness has been identified in Intelbras UnniTI 24.07.11. The affected element is an unknown function of the file /xml/sistema/usuarios.xml. Executing manipulation of the argument Usuario/Senha can lead to unprotected storage of credentials. The attack can be executed remotely. The exploit has been made available to the public and could be exploited.

Weakness: CWE-256 (Plaintext Storage of a Password), CWE-255

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


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

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

## Is CVE-2025-13221 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13221 and fix it if it is affected.

What it is: CVE-2025-13221 is a medium-severity vulnerability in Intelbras UnniTI, published on 15 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13221 exists.

Affected product: Intelbras UnniTI. 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-13221/ (Markdown: https://insights.sbomify.com/CVE-2025-13221/index.md)
```

## Sources

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

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