Issue Bug Accepted Stale Regression

#109199Not possible to create redirects as non-admin user if no access to site root page

Sybille Peters 03/10/26, 10:52 updated 08/20/26, 12:49

Description

Reproduce

1. Create Backend user which has no access to the root page of a site (e.g. give editor DB mount to subpage)
2. With this Backend user, change the slug

result: The following error message appears:

> Attempt to insert record on pages:815 where table “sys_redirect” is not allowed

Analysis

Looks like a regression which was introduced by using DataHandler in sys_redirect: SlugService::createRedirects

It can be reproduced with latest commit 5f0a657f21fffafca697284a4176089f28fe85a0 in 13.4 branch

It is not reproducible with commit cbaa94d8962ec9014d736b041880a5be112b5621 where DataHandler is not yet used.

Versions

  • first reproduced in v13 but probably also occurs in v14

Log message

Tue, 10 Mar 2026 10:05:18 +0100 [ERROR] request="31faef49b52bc" component="TYPO3.CMS.Redirects.Service.SlugService": 
Could not create redirect record for source "site13.de/icbm/umweltbiochemie/forschung/tmap" - {"host":"site13.de","path":"/icbm/umweltbiochemie/forschung/tmap","persistedUid":null,"errorLog":["[1.1]: 
Attempt to insert record on pages:3 where table \"sys_redirect\" is not allowed"],"url":"https://site13.de/typo3/record/edit?token=77d886a527cfbfc0f2288ec6e6a507547fd5bae3&returnUrl=%2Ftypo3%2Fmodule%2Fweb%2Flayout%3Ftoken%3Db41757ee6cefde62123b4f1b8f2c767d2c9ea488%26id%3D15141&edit%5Bpages%5D%5B15141%5D=edit"}

Possible workaround

When overriding pages TCA, it is possible to add redirects:

$GLOBALS['TCA']['pages']['ctrl']['security']['ignoreWebMountRestriction'] = true;

Reviews 2

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". The changes above were merged or abandoned: read them before you start. How to create a patch

Commit message
[BUGFIX] Not possible to create redirects as non-admin user if no access to site root page Resolves: #109199 Releases: main

History 18

  1. Petra Neumann commented <span data-processor="relativetime" data-value="2026-03-13T15:26:55+00:00" > 03/13/26, 15:26 </span>

    I ran into the same issue on a 13.4.27.

    Found this in https://docs.typo3.org/c/typo3/cms-redirects/main/en-us/Setup/Index.html#available-settings:

    Changed in version 12.1
    
    Since TYPO3 v12.1, automatically created redirect records are stored on the configured root page ID of the site. Previously, they were initially stored on the top root page or later on the changed page.

    So since this seems not to be a bug, it’s in my eyes a terrible thing that editors need write access to the site root page to be able to change slugs of subpages. In many instances they have no write access there for good reasons.

    Furthermore these automatically created redirects are stored in the DB as manual redirects with creation_type=1 , but this is another issue i guess.

  2. Sybille Peters commented <span data-processor="relativetime" data-value="2026-03-15T08:54:19+00:00" > 03/15/26, 08:54 </span>

    @Petra Thank you for your note.

    > I ran into the same issue on a 13.4.27.

    Does that mean, the problem did not exist before, in 13.4.26? 13.4.27 was released on 10.03.2026, see https://get.typo3.org/list/version/13

    However, I don’t think the cause of the error is that the redirects are created on the start page. (It is relevant of course, but it is not the single cause of the problem and it is not what was changed when problem first appeared, see explanation below).

    And I don’t think it is intentional or could not be intentional that editors who do not have access to site root will get an error message on slug changes and automatic redirects will no longer be created.

    Also, this would be a huge breaking change, which would warrant a “Breaking” changelog and should not be backported to v13 at this point (due to TYPO3 core team policies). (The problem did not appear in initial 13.4 release (LTS) which was on 15.10.2024). https://get.typo3.org/list/version/13

    The problem was introduced on February 5, 2026 (or rather Febrary 9, 2026 for v13) and probably released with 13.4.25 on February 10, 2026. See below, where I show the patch and date where this problem was introduced.

    Can you confirm that this is intentional and not considered a bug from a core team member?

    Can you confirm my findings below on cause of problem and when this was introduced?

    I investigated and added some more information to the patch which IMHO resulted in the problem:

    https://review.typo3.org/c/Packages/TYPO3.CMS/+/90682

    This patch changed how the redirect is inserted. Previously, it was directly written to the database via Connection. After the change, it is written via DataHandler which performs more checks, some of them being if the editor has access to the page where the redirect is inserted, which would be the site root.

    You can see it in the change in SlugService:

    https://review.typo3.org/c/Packages/TYPO3.CMS/+/90682/18/typo3/sysext/redirects/Classes/Service/SlugService.php

    And I now confirmed it again by using the commit before this change and the commit after:

    • after change: can reproduce problem
    commit 6a16c5ac313d89bc73ea94a5b13f50e0773c11ed (HEAD)
    Author: Oliver Bartsch <bo@cedev.de>
    Date:   Sun Sep 14 19:50:14 2025 +0200
    
        [BUGFIX] Use DataHandler for auto redirect creation

    The date is a little misleading, it is the date of the creation of the patch. It was merged on February 5, 2026 for main and Feb 9,2026 for v13 (visible in the comments on the patch for v13: https://review.typo3.org/c/Packages/TYPO3.CMS/+/92752). Which means it would be first released for v13 with 13.4.25. (13.4.25 on 10.02.2026).

    • commit directly before change , cannot reproduce problem , redirect is created
    commit cbaa94d8962ec9014d736b041880a5be112b5621
    Author: Torben Hansen <derhansen@gmail.com>
    Date:   Sat Feb 7 10:10:03 2026 +0100
    
    [TASK] Improve test coverage for extbase BooleanValidator

    This is the note I added to the patch. No answer so far:

    > Hi, I think this patch might have caused problems with permissions because via DataHandler more permissions are checked for current user, see https://forge.typo3.org/issues/109199 Can you take a look? Thanks.

    > Specifically, in DataHandler::hasPagePermission is called with the site root and this returns false if site root page is not in web mount:

    > if (!$pagesSchema->hasCapability(TcaSchemaCapability::RestrictionWebMount) && !$this->BE_USER->isInWebMount($page, ‘’, $useDeleteClause)) {
    > return false;
    > }

  3. Sybille Peters commented <span data-processor="relativetime" data-value="2026-03-15T08:56:11+00:00" > 03/15/26, 08:56 </span>

    Can someone verify my findings? It looks like it is getting no attention currently and I think it is a big problem for v13 and should not have been backported. (v14 less because that is not in LTS yet).

  4. Oliver Hader commented <span data-processor="relativetime" data-value="2026-03-16T10:04:19+00:00" > 03/16/26, 10:04 </span>

    Besides $this->temporaryPermissionMutationService->addTableModify() there should be a handling allowing to insert sys_redirect records on the site-root-page, e.g.

    • \TYPO3\CMS\Redirects\Service\TemporaryPermissionMutationService::addWebMount(int $pageId): bool
    • \TYPO3\CMS\Redirects\Service\TemporaryPermissionMutationService::removeWebMount(int $pageId): void

    The reason is, that the user does not have access to the assigned site-root-page, see
    https://github.com/TYPO3/typo3/blob/02283c14819f6290336b9770546a38c36a8060d0/typo3/sysext/redirects/Classes/Service/SlugService.php#L147

  5. Wolfgang Klinger commented <span data-processor="relativetime" data-value="2026-03-16T10:21:43+00:00" > 03/16/26, 10:21 </span>

    I fixed this already some time ago (and reported it in a related ticket) in sluggi here:
    https://github.com/wazum/sluggi/blob/main/Classes/DataHandler/BypassAccessCheckForRedirectCreation.php

    If you need a solution right away, you can install my extension (it’s always a good idea, no matter how much you use it).

  6. Wolfgang Klinger commented <span data-processor="relativetime" data-value="2026-03-17T10:23:11+00:00" > 03/17/26, 10:23 </span>

    @ohader
    that seems pretty over-engineered to me, don’t you think (where’s the benefit of all that added complexity)?

    > Besides $this->temporaryPermissionMutationService->addTableModify() there should be a handling allowing to insert sys_redirect records on the site-root-page, e.g.
    >
    > \TYPO3\CMS\Redirects\Service\TemporaryPermissionMutationService::addWebMount(int $pageId): bool
    > \TYPO3\CMS\Redirects\Service\TemporaryPermissionMutationService::removeWebMount(int $pageId): void

    My proposed solution (I have a pull request ready, if you want it):
    - fix checkModifyAccessList (to also adhere to bypassAccessCheckForRecords and return true)
    - and then set bypassAccessCheckForRecords on the local DataHandler instance used for (only) creating the sys_redirect records
    - remove TemporaryPermissionMutationService completely from SlugService (unnecessary then)

  7. Oliver Hader commented <span data-processor="relativetime" data-value="2026-03-17T11:18:37+00:00" > 03/17/26, 11:18 </span>

    Wolfgang Klinger wrote in #note-10:
    > @Oliver Hader
    > that seems pretty over-engineered to me, don’t you think (where’s the benefit of all that added complexity)?

    …

    > My proposed solution (I have a pull request ready, if you want it):
    > – fix checkModifyAccessList (to also adhere to bypassAccessCheckForRecords and return true)
    > – and then set bypassAccessCheckForRecords on the local DataHandler instance used for (only) creating the sys_redirect records
    > – remove TemporaryPermissionMutationService completely from SlugService (unnecessary then)

    From the DataHandler::bypassAccessCheckForRecords PHPdoc.

        /**
         * If TRUE, access check, check for deleted etc. for records is bypassed.
         * YOU MUST KNOW what you are doing if you use this feature!
         */
        public bool $bypassAccessCheckForRecords = false;

    Honestly, I don’t really understand what the property is supposed to do and what the expected behavior would be.

    Extending the scope of bypassAccessCheckForRecords to checkModifyAccessList probably might introduce new and additional side-effects.
    For instance, the checkModifyAccessList hook would not be executed anymore in that case.

    I was aiming for an explicit declaration of what is allowed – I call it “explicit”, you call it “over-engineered” – that are two different opinions, that is fine.

  8. Oliver Hader commented <span data-processor="relativetime" data-value="2026-03-17T11:26:04+00:00" > 03/17/26, 11:26 </span>

    As an alternative, there could be a new public function DataHandler::declareSystemInvocation() which results in treating the DataHandler invocation as system-user (admin-user). This way, it would be more explicit, that NO permission checks at all would be performed.

  9. Oliver Hader commented <span data-processor="relativetime" data-value="2026-03-17T11:50:44+00:00" > 03/17/26, 11:50 </span>

    Wolfgang Klinger wrote in #note-10:
    > My proposed solution (I have a pull request ready, if you want it):
    > – fix checkModifyAccessList (to also adhere to bypassAccessCheckForRecords and return true)
    > – and then set bypassAccessCheckForRecords on the local DataHandler instance used for (only) creating the sys_redirect records
    > – remove TemporaryPermissionMutationService completely from SlugService (unnecessary then)

    I just checked your suggestion. How would you handle the revert action (https://review.typo3.org/c/Packages/TYPO3.CMS/+/90682/18/typo3/sysext/redirects/Classes/Controller/RecordHistoryRollbackController.php)?
    By using bypassAccessCheckForRecords = true it would allow reverts for any history item…

  10. Wolfgang Klinger commented <span data-processor="relativetime" data-value="2026-03-17T12:59:14+00:00" > 03/17/26, 12:59 </span>

    @ohader
    AFAI understand that flag bypassAccessCheckForRecords — it does exactly that: no permissions are evaluated (= acting like an admin).
    Don’t ask me why this is there, but sure, it sounds hacky.

    Fair point about the revert, I’ll investigate another hour and if I can come up with a different solution (something cleaner), I’ll come back to you again here to discuss it.

  11. Wolfgang Klinger commented <span data-processor="relativetime" data-value="2026-03-17T13:36:08+00:00" > 03/17/26, 13:36 </span>

    @ohader

    The problem is, that page-level CONTENT_EDIT depends on the page record’s perms_* fields, not on user group data. There is no narrow grant possible through $BE_USER->groupData changes alone.

    We could (following your “admin” idea above) add these methods to TemporaryPermissionMutationService.
    Something like this:

      public function asSystemUser(callable $operation): mixed
      {
          $previousAdminState = (int)$GLOBALS['BE_USER']->user['admin'];
          $GLOBALS['BE_USER']->user['admin'] = 1;
          try {
              return $operation();
          } finally {
              $GLOBALS['BE_USER']->user['admin'] = $previousAdminState;
          }
      }
    
      // and
      // SlugService
      $this->temporaryPermissionMutationService->asSystemUser(function () use ($data, ...) {
          $dataHandler = GeneralUtility::makeInstance(DataHandler::class);
          $dataHandler->start($data, []);
          …
          $dataHandler->process_datamap();
      });
    
      // RecordHistoryRollbackController
      $this->temporaryPermissionMutationService->asSystemUser(function () use ($correlationId) {
          …
      });

    Is that something you had in mind?