# CVE-2026-108569: Furion .NET Framework StringRenderExtensions.cs String.Replace sql injection

> SQL injection in Furion .NET Framework allows remote attackers to manipulate database queries via the String.Replace function.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/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:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-384j-rrq8-q3g3

## What is CVE-2026-108569?

CVE-2026-108569 is a medium-severity SQL injection vulnerability in Furion .NET Framework, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in Furion .NET Framework up to 4.9.9.92. The impacted element is the function String.Replace of the file framework/Furion/Templates/Extensions/StringRenderExtensions.cs. The manipulation of the argument Name leads to sql injection. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-108569 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108569 is a medium-severity SQL injection vulnerability in Furion .NET Framework, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108569 in the wild and no public exploit code.

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

## Sources

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

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