The core vulnerability stems from how array keys were processed during validation. The commit shows critical changes to:
- Replace instance-based dotPlaceholder with static placeholderHash to prevent cross-validator conflicts
- Modify attribute handling in validateUsingCustomRule to preserve original attributes for specific rules
- Add tests verifying validation bypass using keys like '0', '.', '*' and 'asterisk'
The validateUsingCustomRule was vulnerable because it didn't properly restore original attribute names when handling File/Password rules, allowing attackers to bypass validation by using array keys that matched the validator's placeholder patterns. parseData's placeholder strategy was insufficient as it didn't account for multiple validator instances sharing static placeholders.