The vulnerability stems from the absence of timestamp validation in the proposal processing flow. The commit introduced a new TimeWindowCheck filter in core/handlers/auth/filter/timewindow.go to enforce this check. Prior to the fix, the authFilters configuration (in core.yaml) lacked this filter, meaning the ProcessProposal handler in the endorser server processed requests without verifying if the timestamp fell within the allowed window. This matches the CWE-294 (Authentication Bypass by Capture-replay) and CWE-672 (Expiration check failures) descriptions. The high confidence comes from the explicit addition of the TimeWindowCheck filter in the patch and the CVE's focus on missing timestamp validation.