Spring Framework Vulnerability CVE-2025-22233: Bypass of Disallowed Fields Checks

libspring-java Updated 02 Oct 2025

Summary

16/05/2025
N/A
No i
Unrated
Not published

CVE-2025-22233: CVE-2024-38820 ensured Locale-independent, lowercase conversion for both the configured disallowedFields patterns and for request parameter names. Affects libspring-java versions 4.3.30-1 – 4.3.30-3. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Spring Framework is a powerful framework for building Java applications, providing comprehensive infrastructure support for developing Java applications. It offers features such as dependency injection, aspect-oriented programming, and transaction management. However, certain versions of the Spring Framework are vulnerable to a security issue that allows bypassing checks on disallowed fields, potentially leading to unauthorized data access.

Vulnerability Detail

CVE-2025-22233 arises from the failure to adequately enforce disallowed fields checks in the Spring Framework. Despite improvements in locale-independent, lowercase conversion for disallowed fields and request parameter names, certain scenarios still allow attackers to bypass these checks. This vulnerability affects multiple versions of the Spring Framework, potentially leading to unauthorized access to sensitive data, which could compromise application integrity and user privacy.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a workaround, it is recommended to use a dedicated model object with properties specifically for data binding or to utilize constructor binding. This approach ensures that only explicitly declared properties are bound, enhancing security. Additionally, consider using an explicit list of allowed fields instead of disallowed fields to further mitigate risks.

Conclusion

CVE-2025-22233 represents a significant security risk for users of the Spring Framework, allowing unauthorized access to sensitive data through bypassed checks on disallowed fields. It is crucial for users to upgrade to the patched versions and consider implementing recommended workarounds to enhance security.

See every vulnerability recorded for libspring-java →

Share this vulnerability

FAQ

CVE-2025-22233 is a vulnerability in the Spring Framework that allows bypassing checks on disallowed fields, potentially leading to unauthorized data access.

Affected versions include Spring Framework 6.2.0 - 6.2.6, 6.1.0 - 6.1.19, 6.0.0 - 6.0.27, and 5.3.0 - 5.3.42, along with older unsupported versions.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By uploading your manifest file like package-lock.json, you can check for vulnerabilities without needing to access the code.

If immediate upgrading is not possible, consider implementing the recommended workarounds, such as using a dedicated model object for data binding or constructor binding to limit data exposure.

Detailed information about CVE-2025-22233 can be found in the official Spring Framework documentation and security advisories.

Related vulnerabilities

Recent vulnerabilities recorded for libspring-java.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback