# GHSA-fcpv-w245-r2q7: DotNetNuke.Core security code analysis rules triggered

> Static analysis warnings indicate potential weak cryptography and XML processing issues in the DotNetNuke Core library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 14 Apr 2026

## What is GHSA-fcpv-w245-r2q7?

GHSA-fcpv-w245-r2q7 is a vulnerability in DotNetNuke.Core, published on 14 Apr 2026. 

### Official description

The codebase raises code analysis warnings related to security, including CA3075, CA5366, CA5371, CA5368, CA5369, CA5372, CA5379, CA5350, and CA5351.

Most of these deal with disabling DTD processing in XML documents, but also includes cryptographic algorithm choices.

## Which versions are affected by GHSA-fcpv-w245-r2q7?

2 open source packages ship an affected version, including DotNetNuke.Core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `DotNetNuke.Core` | NuGet | From 6.0.0 | 10.2.2 |
| `DotNetNuke.Core` | NuGet | From 6.0.0 | 10.2.2 |

## How do I fix GHSA-fcpv-w245-r2q7?

Upgrade DotNetNuke.Core to 10.2.2 or later.

## Is GHSA-fcpv-w245-r2q7 being exploited?

There is no known exploitation of GHSA-fcpv-w245-r2q7 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-fcpv-w245-r2q7 and fix it if it is affected.

What it is: GHSA-fcpv-w245-r2q7 is a vulnerability in DotNetNuke.Core, published on 14 Apr 2026. 
Exploitation: There is no known exploitation of GHSA-fcpv-w245-r2q7 in the wild and no public exploit code.

Affected packages and fixed versions:
- DotNetNuke.Core (NuGet): affected from 6.0.0; fixed in 10.2.2
- DotNetNuke.Core (NuGet): affected from 6.0.0; fixed in 10.2.2

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/GHSA-fcpv-w245-r2q7/ (Markdown: https://insights.sbomify.com/GHSA-fcpv-w245-r2q7/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-fcpv-w245-r2q7

---
From sbomify Insights: https://insights.sbomify.com/GHSA-fcpv-w245-r2q7/
Summaries are generated and may contain mistakes; the official description above is the record.