Skip to content

Commit 9b6ee5c

Browse files
committedJun 5, 2012
SOAP API: correct access checks for bugnote editing
Commit 508cab0 introduced a check for bugnote_allow_user_edit_delete, but the actual configuration setting in master is bugnote_user_edit_threshold . Affects #14340: Reporters can update notes of other users by using SOAP API
1 parent b680184 commit 9b6ee5c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed
 

‎api/soap/mc_issue_api.php

+1-1
Original file line numberDiff line numberDiff line change
@@ -1109,7 +1109,7 @@ function mc_issue_note_update( $p_username, $p_password, $p_note ) {
11091109
# Check if the user owns the bugnote and is allowed to update their own bugnotes
11101110
# regardless of the update_bugnote_threshold level.
11111111
$t_user_owns_the_bugnote = bugnote_is_user_reporter( $t_issue_note_id, $t_user_id );
1112-
$t_user_can_update_own_bugnote = config_get( 'bugnote_allow_user_edit_delete', null, $t_user_id, $t_project_id );
1112+
$t_user_can_update_own_bugnote = config_get( 'bugnote_user_edit_threshold', null, $t_user_id, $t_project_id );
11131113
if ( $t_user_owns_the_bugnote && !$t_user_can_update_own_bugnote ) {
11141114
return mci_soap_fault_access_denied( $t_user_id );
11151115
}

0 commit comments

Comments
 (0)