Csla affected by Remote Code Execution via WcfProxy (NetDataContractSerializer)
Published 8 Dec 2025 · Updated 9 Dec 2025
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 package
- Affected
- <6.0.0
- Fixed in
- 6.0.0
dotnet add package Csla --version 6.0.0Details
Impact
Versions of CSLA .NET prior to version 6 allow the use of WcfProxy. WcfProxy uses the NetDataContractSerializer (NDCS) which has known vulnerabilities that can allow remote execution of code during deserialization. NDCS itself is considered obsolete, and you should avoid using WcfProxy or upgrade to CSLA 6 or higher where this issue does not exist.
Patches
CSLA .NET version 6 and higher do not use WCF or NetDataContractSerializer.
Workarounds
If you are using a version CSLA .NET older than version 6, you should stop using WcfProxy in your data portal configuration. Doing this avoids the use of WCF and the NetDataContractSerializer, avoiding the vulnerability.
Is GHSA-wq34-7f4g-953v 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
- CriticalCVE-2024-28698CLSA Directory Traversal vulnerability · 22 Jul 2024
References
- Linkgithub.com/MarimerLLC/csla/security/advisories/GHSA-wq34-7f4g-953v
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-66631
- Linkgithub.com/MarimerLLC/csla/issues/4001
- Linkgithub.com/MarimerLLC/csla/pull/4018
- Packagegithub.com/MarimerLLC/csla
- Linklearn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca2310
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.