Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 610da6e

Browse files
committedJan 18, 2013
filter api: always treat FILTER_PROPERTY_MATCH_TYPE as an int value
Based on @dregad's comments, this follows up on @dhx's fix. Fixes #15373: XSS vulnerability
1 parent bbc6b4f commit 610da6e

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed
 

‎core/filter_api.php

+1-1
Original file line numberDiff line numberDiff line change
@@ -3400,7 +3400,7 @@ function <?php echo $t_js_toggle_func;?>() {
34003400
echo lang_get ('filter_match_all');
34013401
}
34023402
?>
3403-
<input type="hidden" name="match_type" value="<?php echo string_attribute( $t_filter[FILTER_PROPERTY_MATCH_TYPE] )?>"/>
3403+
<input type="hidden" name="match_type" value="<?php echo $t_filter[FILTER_PROPERTY_MATCH_TYPE] ?>"/>
34043404
</td>
34053405
<td colspan="6">&#160;</td>
34063406
</tr>

‎view_all_set.php

+1-1
Original file line numberDiff line numberDiff line change
@@ -202,7 +202,7 @@
202202
$f_note_user_id = array( $f_note_user_id );
203203
}
204204

205-
$f_match_type = gpc_get_string ( FILTER_PROPERTY_MATCH_TYPE, FILTER_MATCH_ALL );
205+
$f_match_type = gpc_get_int( FILTER_PROPERTY_MATCH_TYPE, FILTER_MATCH_ALL );
206206

207207
# these are only single values, even when doing advanced filtering
208208
$f_per_page = gpc_get_int( FILTER_PROPERTY_ISSUES_PER_PAGE, -1 );

0 commit comments

Comments
 (0)
Please sign in to comment.