# CVE-2025-8511: Portabilis i-Diario Observações diario-de-observacoes cross site scripting

> Remote attackers can inject malicious scripts via the Descrição field in the Observações component, potentially leading to code execution or account takeover.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Aug 2025
- **Updated:** 10 Oct 2026
- **Also known as:** GHSA-hpf2-m375-95rh

## What is CVE-2025-8511?

CVE-2025-8511 is a medium-severity cross-site scripting vulnerability in Portabilis i-Diario, published on 3 Aug 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in Portabilis i-Diario 1.5.0. Impacted is an unknown function of the file /diario-de-observacoes/ of the component Observações. Performing a manipulation of the argument Descrição results in cross site scripting. It is possible to initiate the attack remotely. The exploit has been made public and could be used. The patch is named 821342cd8d952e8bd214cb16145da785a92f5681. It is suggested to install a patch to address this issue. The vendor confirms: "Audited values shown on that screen are now sanitized on output: only a minimal allowlist of basic formatting tags is kept and all attributes are stripped, so injected <script> or event-handler markup is removed and displayed as inert text."

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Portabilis I-Diario.

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

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

## Is CVE-2025-8511 being exploited?

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

## Other vulnerabilities in Portabilis i-Diario

- [CVE-2025-9109](https://insights.sbomify.com/CVE-2025-9109/): Portabilis i-Diario Password Recovery Endpoint email observable response discrepancy (medium 6.3)
- [CVE-2025-9107](https://insights.sbomify.com/CVE-2025-9107/): Portabilis i-Diario search_autocomplete cross site scripting (medium 5.3)
- [CVE-2025-9104](https://insights.sbomify.com/CVE-2025-9104/): Portabilis i-Diario Informações Adicionais /planos-de-aulas-por-disciplina cross site scripting (medium 5.1)
- [CVE-2025-9105](https://insights.sbomify.com/CVE-2025-9105/): Portabilis i-Diario Informações Adicionais /planos-de-ensino-por-areas-de-conhecimento cross site scripting (medium 5.1)
- [CVE-2025-9106](https://insights.sbomify.com/CVE-2025-9106/): Portabilis i-Diario Informações Adicionais /planos-de-ensino-por-disciplina cross site scripting (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8511 is a medium-severity cross-site scripting vulnerability in Portabilis i-Diario, published on 3 Aug 2025. Any signed-in user can exploit it over the network, 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-8511 exists.

Affected product: Portabilis i-Diario. 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-8511/ (Markdown: https://insights.sbomify.com/CVE-2025-8511/index.md)
```

## Sources

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

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