This vulnerability occurs when an application defines multiple Struts validation forms with identical names. The framework then unpredictably selects only one form for validation, potentially bypassing intended security checks.
When duplicate validation form names exist, the Struts Validator picks one form arbitrarily and ignores the others. This can lead to the application validating user input against the wrong set of rules, creating unexpected security gaps. Developers might assume their defined validation is active, while in reality, a different—and possibly weaker—set of rules is being applied. This situation often signals outdated or inconsistent validation logic within the codebase. It serves as a clear indicator that the validation configuration is not being properly managed, which frequently accompanies other, more subtle flaws in input handling and data sanitization processes.
Impact: Unexpected State
xml