# CVE-2023-5211: Fattura24 < 6.2.8 - Reflected Cross-Site Scripting

> Attackers can inject malicious scripts via the 'id' parameter in Fattura24, potentially leading to session hijacking or code execution.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A: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:** 31 Oct 2023
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-577v-m627-qpf4

## What is CVE-2023-5211?

CVE-2023-5211 is a medium-severity cross-site scripting vulnerability in Unknown Fattura24, published on 31 Oct 2023. 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

The Fattura24 WordPress plugin before 6.2.8 does not sanitize or escape the 'id' parameter before outputting it back in the page, leading to a reflected Cross-Site Scripting vulnerability.

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

## Which versions are affected by CVE-2023-5211?

It affects 1 product.


Products: Fattura24 Fattura24.

## How do I fix CVE-2023-5211?

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

## Is CVE-2023-5211 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5211 and fix it if it is affected.

What it is: CVE-2023-5211 is a medium-severity cross-site scripting vulnerability in Unknown Fattura24, published on 31 Oct 2023. 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-2023-5211 exists.

Affected product: Unknown Fattura24. 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-2023-5211/ (Markdown: https://insights.sbomify.com/CVE-2023-5211/index.md)
```

## Sources

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

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