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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

1852 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-32509 WordPress Gracey theme < 1.4 - Arbitrary Object Instantiation vulnerability — Gracey 5.4 Medium2026-03-25
CVE-2026-32506 WordPress Archicon theme < 1.7 - Arbitrary Object Instantiation vulnerability — Archicon 5.4 Medium2026-03-25
CVE-2026-32502 WordPress Borgholm theme < 1.6 - PHP Object Injection vulnerability — Borgholm 9.8 Critical2026-03-25
CVE-2026-32484 WordPress weForms plugin <= 1.6.26 - PHP Object Injection vulnerability — weForms 8.8 High2026-03-25
CVE-2026-27095 WordPress Bus Ticket Booking with Seat Reservation plugin <= 5.6.0 - PHP Object Injection vulnerability — Bus Ticket Booking with Seat Reservation 9.8 Critical2026-03-25
CVE-2026-27084 WordPress Buisson theme <= 1.1.11 - PHP Object Injection vulnerability — Buisson 9.8 Critical2026-03-25
CVE-2026-27082 WordPress Love Story theme <= 1.3.12 - PHP Object Injection vulnerability — Love Story 9.8 Critical2026-03-25
CVE-2026-27083 WordPress Work & Travel Company theme <= 1.2 - PHP Object Injection vulnerability — Work & Travel Company 9.8 Critical2026-03-25
CVE-2026-27045 WordPress WooCommerce Infinite Scroll plugin <= 1.6.2 - PHP Object Injection vulnerability — WooCommerce Infinite Scroll 8.8 High2026-03-25
CVE-2026-25429 WordPress Nexa Blocks plugin <= 1.1.1 - PHP Object Injection vulnerability — Nexa Blocks 9.8 Critical2026-03-25
CVE-2026-25400 WordPress Apicona theme <= 24.1.0 - PHP Object Injection vulnerability — Apicona 8.8 High2026-03-25
CVE-2026-25360 WordPress Vex theme < 1.2.9 - PHP Object Injection vulnerability — Vex 8.8 High2026-03-25
CVE-2026-25358 WordPress Meloo theme < 2.8.2 - PHP Object Injection vulnerability — Meloo 8.8 High2026-03-25
CVE-2026-25359 WordPress Pendulum theme < 3.1.5 - PHP Object Injection vulnerability — Pendulum 8.8 High2026-03-25
CVE-2026-25032 WordPress Ricky theme < 2.31 - PHP Object Injection vulnerability — Ricky 9.8 Critical2026-03-25
CVE-2026-25029 WordPress KIDZ theme <= 5.24 - PHP Object Injection vulnerability — KIDZ 9.8 Critical2026-03-25
CVE-2026-25031 WordPress Tasty Daily theme < 1.27 - PHP Object Injection vulnerability — Tasty Daily 9.8 Critical2026-03-25
CVE-2026-25030 WordPress Goldish theme < 3.47 - PHP Object Injection vulnerability — Goldish 9.8 Critical2026-03-25
CVE-2026-24989 WordPress SUMO Affiliates Pro plugin < 11.4.0 - PHP Object Injection vulnerability — SUMO Affiliates Pro 9.8 Critical2026-03-25
CVE-2026-24981 WordPress Visionary Core plugin <= 1.4.9 - PHP Object Injection vulnerability — Visionary Core 8.8 High2026-03-25
CVE-2026-24978 WordPress Jobica Core plugin <= 1.4.1 - PHP Object Injection vulnerability — Jobica Core 8.8 High2026-03-25
CVE-2026-24976 WordPress Organici Library plugin <= 2.1.2 - PHP Object Injection vulnerability — Organici Library 8.8 High2026-03-25
CVE-2026-24974 WordPress CitiLights theme <= 3.7.1 - PHP Object Injection vulnerability — CitiLights 8.8 High2026-03-25
CVE-2026-24378 WordPress EventPrime plugin <= 4.2.8.0 - PHP Object Injection vulnerability — EventPrime 9.8 Critical2026-03-25
CVE-2026-23971 WordPress WoodMart theme <= 8.3.8 - PHP Object Injection vulnerability — WoodMart 8.1 High2026-03-25
CVE-2026-22510 WordPress Melody theme <= 1.6.3 - PHP Object Injection vulnerability — Melody 8.1 High2026-03-25
CVE-2026-22507 WordPress Beelove theme <= 1.2.6 - PHP Object Injection vulnerability — Beelove 9.8 Critical2026-03-25
CVE-2026-22505 WordPress Morning Records theme <= 1.2 - PHP Object Injection vulnerability — Morning Records 8.1 High2026-03-25
CVE-2026-22500 WordPress m2 | Construction and Tools Store theme <= 1.1.2 - PHP Object Injection vulnerability — m2 | Construction and Tools Store 9.8 Critical2026-03-25
CVE-2026-22480 WordPress Product Feed for WooCommerce plugin <= 2.3.3 - PHP Object Injection vulnerability — Product Feed for WooCommerce 7.2 High2026-03-25

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