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-59245 Microsoft SharePoint Online Elevation of Privilege Vulnerability — Microsoft SharePoint Online 9.8 Critical2025-11-20
CVE-2025-36072 IBM webMethods Integration Deserialization — webMethods Integration 8.8 High2025-11-20
CVE-2025-64408 Apache Causeway: Java deserialization vulnerability to authenticated attackers — Apache Causeway 8.8AIHighAI2025-11-19
CVE-2025-13145 WP Import – Ultimate CSV XML Importer for WordPress <= 7.33.1 - Authenticated (Administrator+) PHP Object Injection via CSV Import — WP Ultimate CSV Importer – Import CSV, XML & Excel into WordPress 7.2 High2025-11-19
CVE-2025-12844 AI Engine <= 3.1.8 - Authenticated (Subscriber+) PHP Object Injection via PHAR Deserialization — AI Engine – The Chatbot, AI Framework & MCP for WordPress 7.1 High2025-11-13
CVE-2025-11367 N-central windows software probe Remote Code Execution — N-central 9.8 -2025-11-12
CVE-2025-62204 Microsoft SharePoint Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 8.0 High2025-11-11
CVE-2025-64512 pdfminer.six vulnerable to Arbitrary Code Execution via Crafted PDF Input — pdfminer.six 8.6 High2025-11-10
CVE-2025-12099 Academy LMS – WordPress LMS Plugin for Complete eLearning Solution <= 3.3.8 - Authenticated (Administrator+) PHP Object Injection via 'import_all_courses' — Academy LMS – WordPress LMS Plugin for Complete eLearning Solution 7.2 High2025-11-08
CVE-2025-64439 LangGraph Checkpoint affected by RCE in "json" mode of JsonPlusSerializer — langgraph 8.8 -2025-11-07
CVE-2025-62035 WordPress Togo theme < 1.0.4 - PHP Object Injection vulnerability — Togo 8.8 High2025-11-06
CVE-2025-60245 WordPress WP User Manager plugin <= 2.9.12 - PHP Object Injection vulnerability — WP User Manager 9.8 Critical2025-11-06
CVE-2025-58998 WordPress s2Member Plugin <= 250701 - PHP Object Injection Vulnerability — s2Member 9.8 Critical2025-11-06
CVE-2025-58636 WordPress WP Gravity Forms Keap/Infusionsoft Plugin <= 1.2.3 - Deserialization of untrusted data Vulnerability — WP Gravity Forms Keap/Infusionsoft 9.8 Critical2025-11-06
CVE-2025-58619 WordPress Falang multilanguage Plugin <= 1.3.65 - PHP Object Injection Vulnerability — Falang multilanguage 8.8 High2025-11-06
CVE-2025-58592 WordPress TranslatePress Plugin <= 2.10.2 - Deserialization of untrusted data Vulnerability — TranslatePress 8.1 High2025-11-06
CVE-2025-54719 WordPress Yogi - Health Beauty & Yoga Theme <= 2.9.2 - Deserialization of untrusted data Vulnerability — Yogi - Health Beauty & Yoga 8.8 High2025-11-06
CVE-2025-53586 WordPress WeMusic Theme <= 1.9.1 - PHP Object Injection Vulnerability — WeMusic 8.8 High2025-11-06
CVE-2025-53242 WordPress Seil Theme <= 1.7.1 - Deserialization of untrusted data Vulnerability — Seil 9.8 Critical2025-11-06
CVE-2025-49393 WordPress Sign-up Sheets Plugin <= 2.3.2 - PHP Object Injection Vulnerability — Sign-up Sheets 9.8 Critical2025-11-06
CVE-2025-49386 WordPress Preserve Code Formatting Plugin <= 4.0.1 - PHP Object Injection Vulnerability — Preserve Code Formatting 8.8 High2025-11-06
CVE-2025-48086 WordPress Ajax Search Lite plugin <= 4.13.3 - PHP Object Injection vulnerability — Ajax Search Lite 5.5 Medium2025-11-06
CVE-2025-64164 DataEase is vulnerable to Oracle JNDI Injection — dataease 8.1 -2025-11-06
CVE-2025-8871 Everest Forms (Pro) <= 1.9.7 - Unauthenticated PHP Object Injection via PHAR Deserialization in Form Signature — Everest Forms Pro 5.6 Medium2025-11-05
CVE-2025-64353 WordPress Polylang plugin <= 3.7.3 - Deserialization of untrusted data vulnerability — Polylang 8.8 High2025-10-31
CVE-2025-63675 cryptidy 安全漏洞 — cryptidy 6.9 Medium2025-10-31
CVE-2025-12058 Vulnerability in Keras Model.load_model Leading to Arbitrary Local File Loading and SSRF — Keras 7.5AIHighAI2025-10-29
CVE-2025-62368 Taiga Authenticated Remote Code Execution — taiga-back 9.1 Critical2025-10-28
CVE-2025-12305 quequnlong shiyi-blog Job SysJobController.java deserialization — shiyi-blog 6.3 Medium2025-10-27
CVE-2025-34292 BeWelcome/Rox PHP Object Injection RCE — Rox 9.8AICriticalAI2025-10-27

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