HighGHSA-ppq7-88c7-q879CVE-2021-25976

Cross-Site Request Forgery in PiranhaCMS

Published 17 Nov 2021 · Updated 8 Nov 2023

Is your project on an affected Piranha?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

PiranhaNuGet
Affected
>=4.0.0-alpha1 <10.0-alpha1
Fixed in
10.0-alpha1
Update to the fixed version for your release line, for example:dotnet add package Piranha --version 10.0-alpha1

Details

In PiranhaCMS, versions 4.0.0-alpha1 to 9.2.0 are vulnerable to cross-site request forgery (CSRF) when performing various actions supported by the management system, such as deleting a user, deleting a role, editing a post, deleting a media folder etc., when an ID is known.

Is GHSA-ppq7-88c7-q879 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected Piranha, and gives you the command that fixes it.

More advisories for Piranha

  • LowCVE-2025-67291Piranha has stored cross-site scripting (XSS) vulnerability · 22 Dec 2025
  • LowCVE-2025-67290Piranha has stored cross-site scripting (XSS) vulnerability · 22 Dec 2025
  • MediumCVE-2025-61413Piranha CMS vulnerable to stored cross-site scripting (XSS) · 23 Oct 2025
  • MediumCVE-2025-57692PiranhaCMS stored XSS · 26 Sept 2025
  • MediumCVE-2024-55342Piranha CMS Cross-site Scripting vulnerability · 20 Dec 2024
  • MediumCVE-2024-55341Piranha CMS Cross-site Scripting vulnerability · 20 Dec 2024
All 8 advisories for Piranha

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.