CriticalGHSA-9xhh-3m78-gvgjCVE-2024-28698

CLSA Directory Traversal vulnerability

Published 22 Jul 2024 · Updated 10 Sept 2026

Is your project on an affected Csla?

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 packages

CslaNuGet
Affected
<5.5.4
Fixed in
5.5.4
Update to the fixed version for your release line, for example:dotnet add package Csla --version 5.5.4
CslaNuGet
Affected
>=6.0.0 <8.0.0
Fixed in
8.0.0
Update to the fixed version for your release line, for example:dotnet add package Csla --version 8.0.0
CslaNuGet
Affected
>=7.0.0 <8.0.0
Fixed in
8.0.0
Update to the fixed version for your release line, for example:dotnet add package Csla --version 8.0.0

Details

Directory Traversal vulnerability in Marimer LLC CSLA .Net before 8.0 allows a remote attacker to execute arbitrary code via a crafted script to the MobileFormatter component.

Fixes for this issue have been backported to the 5.x, 6.x, and 7.x branches of CSLA. CSLA version 5.5.4 contains a fix. As of time of publication, 6.x and 7.x do not have numbered versions containing the fix but do have fix commits available.

Is GHSA-9xhh-3m78-gvgj 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 Csla, and gives you the command that fixes it.

More advisories for Csla

  • HighCVE-2025-66631Csla affected by Remote Code Execution via WcfProxy (NetDataContractSerializer) · 8 Dec 2025
Csla security overview

References

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