Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-502 (可信数据的反序列化) — Vulnerability Class 1687

1687 vulnerabilities classified as CWE-502 (可信数据的反序列化). AI Chinese analysis included.

CWE-502 represents a critical security weakness where applications deserialize untrusted data without validating its integrity or structure. Attackers typically exploit this vulnerability by crafting malicious serialized objects that, when processed by the application, trigger unintended code execution or logic flaws. This often leads to remote code execution, denial of service, or privilege escalation, as the deserialization process may instantiate dangerous classes or invoke unsafe methods. To mitigate this risk, developers must strictly avoid deserializing data from untrusted sources. Instead, they should implement robust input validation, use allowlists for permitted data types, or adopt safer serialization formats like JSON that do not inherently support arbitrary object instantiation. Additionally, employing cryptographic signatures to verify data authenticity before deserialization ensures that only trusted, unaltered payloads are processed, effectively neutralizing the threat of malicious object injection.

MITRE CWE Description
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Common Consequences (3)
IntegrityModify Application Data, Unexpected State
Attackers can modify unexpected objects or data that was assumed to be safe from modification. Deserialized data or code could be modified without using the provided accessor functions, or unexpected functions could be invoked.
AvailabilityDoS: Resource Consumption (CPU)
If a function is making an assumption on when to terminate, based on a sentry in a string, it could easily never terminate.
OtherVaries by Context
The consequences can vary widely, because it depends on which objects or methods are being deserialized, and how they are used. Making an assumption that the code in the deserialized object is valid is dangerous and can enable exploitation. One example is attackers using gadget chains to perform una…
Mitigations (5)
Architecture and Design, ImplementationIf available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
ImplementationWhen deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
ImplementationExplicitly define a final object() to prevent deserialization.
Architecture and Design, ImplementationMake fields transient to protect them from deserialization. An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.
ImplementationAvoid having unnecessary types or gadgets (a sequence of instances and method invocations that can self-execute during the deserialization process, often found in libraries) available that can be leveraged for malicious ends. This limits the potential for unintended or unauthorized types and gadgets to be leveraged by the attacker. Add only acceptable classes to an allowlist. Note: new gadgets are…
Examples (2)
This code snippet deserializes an object from a file and uses it as a UI button:
try { File file = new File("object.obj"); ObjectInputStream in = new ObjectInputStream(new FileInputStream(file)); javax.swing.JButton button = (javax.swing.JButton) in.readObject(); in.close(); }
Bad · Java
private final void readObject(ObjectInputStream in) throws java.io.IOException { throw new java.io.IOException("Cannot be deserialized"); }
Good · Java
In Python, the Pickle library handles the serialization and deserialization processes. In this example derived from [REF-467], the code receives and parses data, and afterwards tries to authenticate a user based on validating a token.
try { class ExampleProtocol(protocol.Protocol): def dataReceived(self, data): # Code that would be here would parse the incoming data # After receiving headers, call confirmAuth() to authenticate def confirmAuth(self, headers): try: token = cPickle.loads(base64.b64decode(headers['AuthToken'])) if not check_hmac(token['signature'], token['data'], getSecretKey()): raise AuthFail self.secure_data = token['data'] except: raise AuthFail }
Bad · Python
CVE IDTitleCVSSSeverityPublished
CVE-2025-39550 WordPress FluentCommunity plugin <= 1.2.15 - PHP Object Injection Vulnerability — FluentCommunity 9.8 Critical2025-04-17
CVE-2025-39551 WordPress FluentBoards plugin <= 1.47 - PHP Object Injection Vulnerability — FluentBoards 9.8 Critical2025-04-17
CVE-2025-39588 WordPress Ultimate Store Kit Elementor Addons plugin <= 2.4.0 - Deserialization of untrusted data Vulnerability — Ultimate Store Kit Elementor Addons 9.8 Critical2025-04-17
CVE-2025-39565 WordPress MelaPress Login Security plugin <= 2.1.0 - PHP Object Injection Vulnerability — MelaPress Login Security 6.6 Medium2025-04-16
CVE-2025-3677 lm-sys fastchat apply_delta.py apply_delta_low_cpu_mem deserialization — fastchat 5.3 Medium2025-04-16
CVE-2025-30985 WordPress GNUCommerce plugin <= 1.5.4 - PHP Object Injection vulnerability — GNUCommerce 9.8 Critical2025-04-15
CVE-2025-3622 Xorbits Inference model.py load deserialization — Inference 5.5 Medium2025-04-15
CVE-2025-3590 Adianti Framework deserialization — Framework 6.3 Medium2025-04-14
CVE-2025-31935 Subnet Solutions PowerSYSTEM Center Deserialization of Untrusted Data — PowerSYSTEM Center 2020 6.2 Medium2025-04-11
CVE-2025-3439 Everest Forms – Contact Form, Quiz, Survey, Newsletter & Payment Form Builder for WordPress <= 3.1.1 - Unauthenticated PHP Object Injection — Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder 9.8 Critical2025-04-11
CVE-2025-31932 OPEN BizRobo! 代码问题漏洞 — BizRobo! 8.8AIHighAI2025-04-11
CVE-2025-32607 WordPress WpBookingly plugin <= 1.3.0 - PHP Object Injection vulnerability — WpBookingly 9.8 Critical2025-04-11
CVE-2025-32568 WordPress EmpikPlace for Woocommerce Plugin <= 1.4.3 - PHP Object Injection vulnerability — EmpikPlace for Woocommerce 9.8 Critical2025-04-11
CVE-2025-32569 WordPress TableOn plugin <= 1.0.4.3 - PHP Object Injection vulnerability — TableOn 9.8 Critical2025-04-11
CVE-2025-32144 WordPress Job Board Manager Plugin <= 2.1.61 - PHP Object Injection vulnerability — Job Board Manager 8.8 High2025-04-11
CVE-2025-32143 WordPress Accordion plugin <= 2.3.11 - PHP Object Injection vulnerability — Accordion 8.8 High2025-04-11
CVE-2025-32145 WordPress WpEvently plugin <= 4.3.6 - PHP Object Injection vulnerability — WpEvently 8.8 High2025-04-10
CVE-2025-32375 Insecure Deserialization leads to RCE in BentoML's runner server — BentoML 9.8 Critical2025-04-09
CVE-2025-30284 ColdFusion | Deserialization of Untrusted Data (CWE-502) — ColdFusion 8.4 High2025-04-08
CVE-2025-24447 ColdFusion | Deserialization of Untrusted Data (CWE-502) — ColdFusion 9.1 Critical2025-04-08
CVE-2025-30285 ColdFusion | Deserialization of Untrusted Data (CWE-502) — ColdFusion 8.4 High2025-04-08
CVE-2025-29793 Microsoft SharePoint Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 7.2 High2025-04-08
CVE-2025-3413 opplus springboot-admin SysGeneratorController.java code deserialization — springboot-admin 6.3 Medium2025-04-08
CVE-2025-3425 Unauthenticated Remote Code Execution via .NET Deserialization — IntelliSpace Portal 9.8AICriticalAI2025-04-07
CVE-2025-2251 Org.jboss.eap:wildfly-ejb3: improper deserialization in jboss marshalling allows remote code execution 6.2 Medium2025-04-07
CVE-2025-31175 Huawei EMUI和Huawei HarmonyOS 安全漏洞 — HarmonyOS 8.4 High2025-04-07
CVE-2025-3250 elunez eladmin Maintenance Management Module testConnect deserialization — eladmin 4.3 Medium2025-04-04
CVE-2025-27520 BentoML Allows Remote Code Execution (RCE) via Insecure Deserialization — BentoML 9.8 Critical2025-04-04
CVE-2025-2244 Insecure PHP deserialization issue in GravityZone Console (VA-12634) — GravityZone Console 9.8AICriticalAI2025-04-04
CVE-2025-3165 thu-pacman chitu backend.py torch.load deserialization — chitu 5.3 Medium2025-04-03

Vulnerabilities classified as CWE-502 (可信数据的反序列化) represent 1687 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.