CLSA Directory Traversal vulnerability
Published 22 Jul 2024 · Updated 10 Sept 2026
Is your project on an affected Csla?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <5.5.4
- Fixed in
- 5.5.4
dotnet add package Csla --version 5.5.4- Affected
- >=6.0.0 <8.0.0
- Fixed in
- 8.0.0
dotnet add package Csla --version 8.0.0- Affected
- >=7.0.0 <8.0.0
- Fixed in
- 8.0.0
dotnet add package Csla --version 8.0.0Details
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
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2024-28698
- Linkgithub.com/MarimerLLC/csla/pull/3552
- Linkgithub.com/MarimerLLC/csla/commit/2c32a5748a0a4bb0159285dfad61d4050e890080
- Linkgithub.com/MarimerLLC/csla/commit/445bc609bc117f62cabf49e1462f7a43b0f8f9a2
- Linkgithub.com/MarimerLLC/csla/commit/8fbdd8c773bfeb9ba3e52d91b5a664848629b13a
- Linkgithub.com/MarimerLLC/csla/commit/f3a5c3474974f60ce3c8ffbd5d91c23a1e397ea4
- Packagegithub.com/MarimerLLC/csla
- Linkgithub.com/MarimerLLC/csla/releases/tag/v5.5.4
- Linkwww.intruder.io/research/path-traversal-and-code-execution-in-csla-net-cve-2024-28698
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.