# CVE-2025-61413: Piranha CMS vulnerable to stored cross-site scripting (XSS)

> Attackers can execute arbitrary scripts in Piranha CMS by injecting payloads into Markdown blocks within the page manager.

- **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:** 23 Oct 2025
- **Updated:** 24 Oct 2025
- **Also known as:** GHSA-3qcp-9v8c-6jp7

## What is CVE-2025-61413?

CVE-2025-61413 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Oct 2025. 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

A stored cross-site scripting (XSS) vulnerability in the /manager/pages component of Piranha CMS v12.0 allows attackers to execute arbitrary web scripts or HTML via creating a page and injecting a crafted payload into the Markdown blocks.

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

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

2 open source packages ship an affected version, including Piranha. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Piranha` | NuGet | All versions to 12.0.0 | None |
| `Piranha` | NuGet | All versions to 12.0.0 | None |

Products: Dotnetfoundation Piranha Cms.

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

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

## Is CVE-2025-61413 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-25976](https://insights.sbomify.com/CVE-2021-25976/): Piranha CMS - Site-wide Cross-Site Request Forgery (CSRF) (high 8.1)
- [CVE-2025-57692](https://insights.sbomify.com/CVE-2025-57692/): PiranhaCMS stored XSS (medium 6.8)
- [CVE-2025-67290](https://insights.sbomify.com/CVE-2025-67290/): Piranha has stored cross-site scripting (XSS) vulnerability (medium 6.1)
- [CVE-2025-67291](https://insights.sbomify.com/CVE-2025-67291/): Piranha has stored cross-site scripting (XSS) vulnerability (medium 6.1)
- [CVE-2021-25977](https://insights.sbomify.com/CVE-2021-25977/): Piranha CMS - Stored XSS in Page Title (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61413 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Oct 2025. 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-2025-61413 exists.

Affected packages and fixed versions:
- Piranha (NuGet): affected all versions up to 12.0.0; no fix listed
- Piranha (NuGet): affected all versions up to 12.0.0; no fix listed

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-61413/ (Markdown: https://insights.sbomify.com/CVE-2025-61413/index.md)
```

## Sources

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

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