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-2026-27098 WordPress Au Pair Agency - Babysitting & Nanny Theme theme <= 1.2.2 - Deserialization of untrusted data vulnerability — Au Pair Agency - Babysitting & Nanny Theme 8.1 High2026-03-05
CVE-2026-23798 WordPress PowerPress Podcasting plugin <= 11.15.10 - PHP Object Injection vulnerability — PowerPress Podcasting 8.8 High2026-03-05
CVE-2026-24385 WordPress Podlove Web Player plugin <= 5.9.1 - PHP Object Injection vulnerability — Podlove Web Player 7.5 High2026-03-05
CVE-2026-22497 WordPress Jardi theme <= 1.7.2 - PHP Object Injection vulnerability — Jardi 9.8 Critical2026-03-05
CVE-2026-22501 WordPress Mounthood theme <= 1.3.2 - PHP Object Injection vulnerability — Mounthood 9.8 Critical2026-03-05
CVE-2026-22474 WordPress Equestrian Centre theme <= 1.5 - PHP Object Injection vulnerability — Equestrian Centre 9.8 Critical2026-03-05
CVE-2026-22473 WordPress Dental Clinic theme <= 3.7 - PHP Object Injection vulnerability — Dental Clinic 8.8 High2026-03-05
CVE-2026-22475 WordPress Estate theme <= 1.3.4 - PHP Object Injection vulnerability — Estate 9.8 Critical2026-03-05
CVE-2026-22471 WordPress Secudeal Payments for Ecommerce plugin <= 1.1 - PHP Object Injection vulnerability — Secudeal Payments for Ecommerce 8.8 High2026-03-05
CVE-2026-22453 WordPress Pets Club theme <= 2.3 - PHP Object Injection vulnerability — Pets Club 9.8 Critical2026-03-05
CVE-2026-22451 WordPress Handyman theme <= 1.4.7 - PHP Object Injection vulnerability — Handyman 9.8 Critical2026-03-05
CVE-2026-22454 WordPress Solaris theme <= 2.5 - PHP Object Injection vulnerability — Solaris 9.8 Critical2026-03-05
CVE-2026-22417 WordPress Grand Wedding theme < 3.1.11 - PHP Object Injection vulnerability — Grand Wedding 9.8 Critical2026-03-05
CVE-2025-54001 WordPress Classter theme <= 2.5 - PHP Object Injection vulnerability — Classter 9.8 Critical2026-03-05
CVE-2026-20131 Cisco Secure Firewall Management Center Software Remote Code Execution Vulnerability — Cisco Secure Firewall Management Center (FMC) 10.0 Critical2026-03-04
CVE-2026-3452 Concrete CMS below 9.4.8 is vulnerable to stored deserialization leading to RCE in the Express Entry List block. — Concrete CMS 7.2 -2026-03-04
CVE-2026-27971 Qwik affected by unauthenticated RCE via server$ Deserialization — qwik 9.8AICriticalAI2026-03-03
CVE-2025-52998 Chamilo: PHAR deserialization bypass — chamilo-lms 8.1AIHighAI2026-03-02
CVE-2025-50198 Chamilo: Deserialization of untrusted data in /plugin/vchamilo/views/import.php via POST configuration_file; POST course_path; POST home_path parameters — chamilo-lms 9.8AICriticalAI2026-03-02
CVE-2024-47886 Chamilo: Post-Auth Remote Code Execution — chamilo-lms 7.2AIHighAI2026-03-02
CVE-2026-3422 e-Excellence|U-Office Force - Insecure Deserialization — U-Office Force 9.8 Critical2026-03-02
CVE-2026-2471 WP Mail Logging <= 1.15.0 - Unauthenticated PHP Object Injection via Email Log Message Field — WP Mail Logging 7.5 High2026-02-28
CVE-2026-27776 NTT DATA INTRAMART intra-mart Accel Platform 代码问题漏洞 — intra-mart Accel Platform 8.8 -2026-02-27
CVE-2026-3071 flair 安全漏洞 — Flair 8.4 High2026-02-26
CVE-2026-28138 WordPress uListing plugin <= 2.2.0 - PHP Object Injection vulnerability — uListing 7.2 High2026-02-26
CVE-2026-27830 c3p0 vulnerable to Remote Code Execution via unsafe deserialization of userOverridesAsString property — c3p0 9.8AICriticalAI2026-02-26
CVE-2026-27794 LangGraph: BaseCache Deserialization of Untrusted Data may lead to Remote Code Execution — langgraph-checkpoint 6.6 Medium2026-02-25
CVE-2026-26222 DocLink .NET Remoting Unauthenticated Arbitrary File Read/Write RCE — Altec DocLink 9.1AICriticalAI2026-02-24
CVE-2026-25747 Apache Camel LevelDB: Deserialization of Untrusted Data in Camel LevelDB — Apache Camel LevelDB 8.8AIHighAI2026-02-23
CVE-2026-2970 datapizza-labs datapizza-ai cache.py RedisCache deserialization — datapizza-ai 4.6 Medium2026-02-23

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