CVE 2.3 LOW

Dromara Sa-Token SaSerializerTemplateForJdkUseBase64.java ObjectInputStream.readObject deserialization_CVE-2025-15222

2.3 / 10
LOW
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Description

A vulnerability has been found in Dromara Sa-Token up to 1.44.0. This issue affects the function ObjectInputStream.readObject of the file SaSerializerTemplateForJdkUseBase64.java. Such manipulation leads to deserialization. The attack can be executed remotely. This attack is characterized by high complexity. The exploitability is assessed as difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Basic Information

ID CVE-2025-15222
Source VulDB
Published Dec 30, 2025 at 05:32

Affected Product

Vendor Dromara
Product Sa-Token
Version 1.0
Affected Versions Dromara Sa-Token 1.0
Dromara Sa-Token 1.1
Dromara Sa-Token 1.2
Dromara Sa-Token 1.3
Dromara Sa-Token 1.4
Dromara Sa-Token 1.5
Dromara Sa-Token 1.6
Dromara Sa-Token 1.7
Dromara Sa-Token 1.8
Dromara Sa-Token 1.9
Dromara Sa-Token 1.10
Dromara Sa-Token 1.11
Dromara Sa-Token 1.12
Dromara Sa-Token 1.13
Dromara Sa-Token 1.14
Dromara Sa-Token 1.15
Dromara Sa-Token 1.16
Dromara Sa-Token 1.17
Dromara Sa-Token 1.18
Dromara Sa-Token 1.19
Dromara Sa-Token 1.20
Dromara Sa-Token 1.21
Dromara Sa-Token 1.22
Dromara Sa-Token 1.23
Dromara Sa-Token 1.24
Dromara Sa-Token 1.25
Dromara Sa-Token 1.26
Dromara Sa-Token 1.27
Dromara Sa-Token 1.28
Dromara Sa-Token 1.29
Dromara Sa-Token 1.30
Dromara Sa-Token 1.31
Dromara Sa-Token 1.32
Dromara Sa-Token 1.33
Dromara Sa-Token 1.34
Dromara Sa-Token 1.35
Dromara Sa-Token 1.36
Dromara Sa-Token 1.37
Dromara Sa-Token 1.38
Dromara Sa-Token 1.39
Dromara Sa-Token 1.40
Dromara Sa-Token 1.41
Dromara Sa-Token 1.42
Dromara Sa-Token 1.43
Dromara Sa-Token 1.44.0

CWE Classification

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.