#109539Editors are not allowed to enable/disable sys_redirect entries in Redirects module
Description
As a non-admin editor with access to a root page and the Redirects module, I can view the list of existing redirects and enable or disable a redirect by editing the entry (via the pen icon) and saving the changes. However, when attempting to enable or disable a redirect directly from the Redirects list view, an error occurs:
> 1: Attempt to modify sys_redirect record “2” is disallowed
Analysis
In \TYPO3\CMS\Redirects\Hooks\DataHandlerPermissionGuardHook, the method processDatamap_preProcessFieldArray checks the permissions:
if ($table === 'sys_redirect' && !$this->redirectPermissionGuard->isAllowedRedirect($incomingFieldArray ?? []))
The RedirectPermsisionGuard verifies the source_host and target fields:
public function isAllowedRedirect(array $redirect): bool
{
if ($this->getBackendUser()->isAdmin()) {
return true;
}
return $this->isAllowedSourceHost($redirect['source_host'] ?? '')
&& $this->isAllowedTarget($redirect['target'] ?? '');
}
When disabling a sys_redirect entry from the overview, the $incomingFieldArray only contains ['disable' => 1], which causes the permission check to fail. If the entire record is edited instead, $incomingFieldArray includes source_host and target, allowing the check to pass.
Steps to reproduce
1. Set up a new TYPO3 installation (tested with TYPO3 13.4.27).
2. Create a new page and create a redirect for it.
3. Create a new backend user group with permissions for the redirects module and read/write access to sys_redirect.
4. Create a new backend user, assigned to the created backend user group.
5. Log in with the new user and navigate to the Redirects module.
6. Attempt to disable a redirect by toggling the switch icon in the list view.
Reviews 3
Related issues 1
History 613
-
Benni Mack changed Sprint Focus On Location Sprint <span data-processor="relativetime" data-value="2026-08-06T16:02:54+00:00" > 08/06/26, 16:02 </span>
-
Marno Schmigotzki commented and changed assigned to Marno Schmigotzki <span data-processor="relativetime" data-value="2026-08-06T21:05:02+00:00" > 08/06/26, 21:05 </span>
on it
-
Gerrit Code Review pushed patch set 1 for main to change 95164 status
NewUnder Review <span data-processor="relativetime" data-value="2026-08-07T09:32:56+00:00" > 08/07/26, 09:32 </span> -
Marno Schmigotzki changed Related to #110052 <span data-processor="relativetime" data-value="2026-08-07T12:14:32+00:00" > 08/07/26, 12:14 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 95164 <span data-processor="relativetime" data-value="2026-08-07T12:38:01+00:00" > 08/07/26, 12:38 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 95164 <span data-processor="relativetime" data-value="2026-08-07T12:50:13+00:00" > 08/07/26, 12:50 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 95164 <span data-processor="relativetime" data-value="2026-08-08T06:33:21+00:00" > 08/08/26, 06:33 </span>
-
Gerrit Code Review pushed patch set 1 for 14.3 to change 96277 <span data-processor="relativetime" data-value="2026-10-01T20:28:26+00:00" > 10/01/26, 20:28 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 96278 <span data-processor="relativetime" data-value="2026-10-01T20:29:43+00:00" > 10/01/26, 20:29 </span>
-
Marno Schmigotzki commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-10-01T20:35:10+00:00" > 10/01/26, 20:35 </span>Applied in changeset commit:9e2685e77d85adf208790791704f728c92c605db.
-
Gerrit Code Review pushed patch set 2 for 13.4 to change 96278 status
ResolvedUnder Review <span data-processor="relativetime" data-value="2026-10-01T21:31:14+00:00" > 10/01/26, 21:31 </span> -
Marno Schmigotzki commented and changed status
Under ReviewResolved <span data-processor="relativetime" data-value="2026-10-01T21:45:12+00:00" > 10/01/26, 21:45 </span>Applied in changeset commit:658c74d46926f924e97e03b8a6caef23e2174401.
We can confirm this issue.
Workaround as mentioned is the editing of the whole record instead of the fast dis-/enable buttons