dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-15222

MEDIUM · 5.0 CVSS v3.1 Published 2025-12-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an unsafe deserialization vulnerability in Dromara Sa-Token's SaSerializerTemplateForJdkUseBase64.java component. The ObjectInputStream.readObject method is used to deserialize data without proper validation or use of a safe ObjectInputStream subclass with class whitelist filtering, allowing remote attackers to potentially inject malicious serialized objects.

MitigationReplace unsafe ObjectInputStream.readObject with a safe implementation using a custom ObjectInputStream that restricts deserialization to an explicit whitelist of allowed classes, or migrate to safer serialization formats like JSON.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Sa-Token library in dependencies
    Search your project dependencies for 'sa-token' using your build tool (Maven pom.xml, Gradle build.gradle, or JAR files in lib/ directory)
    Affected if Sa-Token library is present in your project dependencies
  2. Identify the vulnerable deserialization class
    Search for the file SaSerializerTemplateForJdkUseBase64.java in your codebase or dependency JARs, or search for usages of ObjectInputStream.readObject in your code
    Affected if Your codebase uses SaSerializerTemplateForJdkUseBase64.java or contains direct calls to ObjectInputStream.readObject for deserializing untrusted data
  3. Check if safe ObjectInputStream is implemented
    Search your codebase for custom ObjectInputStream subclasses that implement class whitelist filtering (look for overrides of resolveClass or similar whitelist logic)
    Affected if No custom safe ObjectInputStream with class whitelist is found and ObjectInputStream.readObject is used directly
  4. Verify deserialization usage patterns
    Review code that performs deserialization to determine if the data source is untrusted (user input, network data, external files)
    Affected if Your application deserializes data from untrusted sources using unsafe ObjectInputStream.readObject
  5. Determine if JsonSerializer is in use
    Check if your project uses JsonSerializer or other JSON-based serialization instead of Java native serialization for data handling
    Affected if Your project relies solely on Java native serialization (ObjectInputStream/ObjectOutputStream) without JSON alternatives

You are affected if your project uses the Sa-Token library and deserializes untrusted data using the unsafe ObjectInputStream.readObject in SaSerializerTemplateForJdkUseBase64.java without a custom whitelisting ObjectInputStream subclass.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace unsafe ObjectInputStream.readObject with a safe implementation using a custom ObjectInputStream that restricts deserialization to an explicit whitelist of allowed classes, or migrate to safer serialization formats like JSON.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,024.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15222 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15222 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data