CSLA .NET is vulnerable to Remote Code Execution via WcfProxy
cve-program · CVE-2025-66631
PublishedCSLA .NET is a framework designed for the development of reusable, object-oriented business layers for applications. Versions 5.5.4 and below allow the use of WcfProxy. WcfProxy uses the now-obsolete NetDataContractSerializer (NDCS) and is vulnerable to remote code execution during deserialization. This vulnerability is fixed in version 6.0.0. To workaround this issue, remove the WcfProxy in data portal configurations.
Read the publisher's advisoryeuvd · EUVD-2025-201825
PublishedCSLA .NET is a framework designed for the development of reusable, object-oriented business layers for applications. Versions 5.5.4 and below allow the use of WcfProxy. WcfProxy uses the now-obsolete NetDataContractSerializer (NDCS) and is vulnerable to remote code execution during deserialization. This vulnerability is fixed in version 6.0.0. To workaround this issue, remove the WcfProxy in data portal configurations.
Read the publisher's advisorynvd · CVE-2025-66631
PublishedCSLA .NET is a framework designed for the development of reusable, object-oriented business layers for applications. Versions 5.5.4 and below allow the use of WcfProxy. WcfProxy uses the now-obsolete NetDataContractSerializer (NDCS) and is vulnerable to remote code execution during deserialization. This vulnerability is fixed in version 6.0.0. To workaround this issue, remove the WcfProxy in data portal configurations.
Read the publisher's advisoryosv · GHSA-wq34-7f4g-953v
Published### 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2025-66631 · CVE overview and exploitation status
cve-program · CVE-2025-66631
- https://github.com/MarimerLLC/csla/security/advisories/GHSA-wq34-7f4g-953v
- https://github.com/MarimerLLC/csla/issues/4001
- https://github.com/MarimerLLC/csla/pull/4018
euvd · EUVD-2025-201825
- https://github.com/MarimerLLC/csla/security/advisories/GHSA-wq34-7f4g-953v
- https://github.com/MarimerLLC/csla/issues/4001
- https://github.com/MarimerLLC/csla/pull/4018
nvd · CVE-2025-66631
- https://github.com/MarimerLLC/csla/issues/4001
- https://github.com/MarimerLLC/csla/pull/4018
- https://github.com/MarimerLLC/csla/security/advisories/GHSA-wq34-7f4g-953v
osv · GHSA-wq34-7f4g-953v
- https://github.com/MarimerLLC/csla/security/advisories/GHSA-wq34-7f4g-953v
- https://nvd.nist.gov/vuln/detail/CVE-2025-66631
- https://github.com/MarimerLLC/csla/issues/4001
- https://github.com/MarimerLLC/csla/pull/4018
- https://github.com/MarimerLLC/csla
- https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca2310
Related changes
Linked by CVE identifierNo related changes are available here.