Issue Bug Resolved

#11008314 PHP warnings from one request: "Undefined array key 1 in /var/html/vendor/typo3/cms-core/Classes/Routing/PageRouter.php"

Florian Seirer 06/22/26, 08:28 updated 10/25/26, 17:35

Description

I found some requests in my access log that generated each of the following errors seven times:

Core: Error handler (FE): PHP Warning: Undefined array key 1 in /var/html/vendor/typo3/cms-core/Classes/Routing/PageRouter.php line 288
Core: Error handler (FE): PHP Warning: Undefined array key 1 in /var/html/vendor/typo3/cms-core/Classes/Routing/PageRouter.php line 422

This unusual request had these parameters, which have nothing to do with my TYPO3 site:

?LOCALECODE=%3Csz1&LOGGED_IN_COOKIE=%3Csz2&La=%3Csz3&LandingUrl=%3Csz4&Lang=%3Csz5&LangCode=%3Csz6&LangID=%3Csz7&Language=%3Csz8&Last4Digits=%3Csz9&LastViewAction=%3CszA&LeadID=%3CszB&LegID=%3CszC&LegendMode=%3CszD&Length=%3CszE&Level=%3CszF&LineHighlight=%3Csz10&Lingua=%3Csz11&LinkID=%3Csz12&List=%3Csz13&ListByBooth=%3Csz14&ListID=%3Csz15&ListId=%3Csz16&Lng=%3Csz17&LoadReverse=%3Csz18&Locale=%3Csz19&Location=%3Csz1A&LocationPath=%3Csz1B&LocationVehicleId=%3Csz1C&Login=%3Csz1D&LoginForm=%3Csz1E&Lookup=%3Csz1F&LostPasswordForm=%3Csz20&M=%3Csz21&M2=%3Csz22&MD=%3Csz23&MEDIENNR=%3Csz24&MENO=%3Csz25&METHOD=%3Csz26&MID=%3Csz27&MOD=%3Csz28&MODE=%3Csz29&MODsid=%3Csz2A&MP=%3Csz2B&MainScanner=%3Csz2C&MainTable=%3Csz2D&Maintable=%3Csz2E&Make=%3Csz2F&MakeName=%3Csz30&MarketPlace=%3Csz31&Marriage=%3Csz32&MatchID=%3Csz33&MaxPrice=%3Csz34&MemberID=%3Csz35&MemberId=%3Csz36&Menu=%3Csz37&MenuID=%3Csz38&MenuId=%3Csz39&MenuItem=%3Csz3A&Message=%3Csz3B&Mid=%3Csz3C&MinPrice=%3Csz3D&MnId=%3Csz3E&ModID=%3Csz3F&Mode=%3Csz40&Model=%3Csz41&ModuleInstanceID=%3Csz42&ModuleVar=%3Csz43&Mohajer22=%3Csz44&Month=%3Csz45&MultiCompany=%3Csz46&MyTeam=%3Csz47&N=%3Csz48&N3tshcook=%3Csz49&NAME=%3Csz4A&NEWCHOICE=%3Csz4B&NEWHOST=%3Csz4C&NEWNAME=%3Csz4D&NEWPASS=%3Csz4E&NEWPRIVILEGES=%3Csz4F&NICK=%3Csz50&NID=%3Csz51&NONCE_TOKEN=%3Csz52&NOTE=%3Csz53&NPFX=%3Csz54&NSFX=%3Csz55&Name=%3Csz56&Nav=%3Csz57&NavID=%3Csz58&NavType=%3Csz59&Ne=%3Csz5A&NetworkPlatform=%3Csz5B&NetworkScreenName=%3Csz5C&NetworkUserID=%3Csz5D&NewBreadCrumb=%3Csz5E&NewFolderName=%3Csz5F&NewsCode=%3Csz60&NewsID=%3Csz61&NewsId=%3Csz62&News_ID=%3Csz63&Nid=%3Csz64&Nieuws=%3Csz65&Nivel=%3Csz66&No=%3Csz67&Noticia=%3Csz68&Nr=%3Csz69&Nrpp=%3Csz6A&Ns=%3Csz6B&Nso=%3Csz6C&Ntk=%3Csz6D&Nto=%3Csz6E&Ntt=%3Csz6F&Ntx=%3Csz70&Ntype=%3Csz71&Num=%3Csz72&Number=%3Csz73&O=%3Csz74&O1=%3Csz75&OAuthCookie=%3Csz76&OB=%3Csz77&OD=%3Csz78&OID=%3Csz79&ON=%3Csz7A&ONDATE=%3Csz7B&OP=%3Csz7C&OUTPUT=%3Csz7D&OUTPUTFILETEXT=%3Csz7E&ObitID=%3Csz7F&Object=%3Csz80&ObjectID=%3Csz81&ObjectPath=%3Csz82&OneJS=%3Csz83&Op=%3Csz84&Open=%3Csz85&OpenWith=%3Csz86&Operation=%3Csz87&Opt1=%3Csz88&Opt2=%3Csz89&Option=%3Csz8A&Or=%3Csz8B&Order=%3Csz8C&OrderBy=%3Csz8D&Org=%3Csz8E&OriginalUrl=%3Csz8F&OutSum=%3Csz90&OutputType=%3Csz91&OverridePath=%3Csz92&Owner=%3Csz93&P=%3Csz94&P1=%3Csz95&P2=%3Csz96&PA=%3Csz97&PAGE=%3Csz98&PAGEN_1=%3Csz99&PAGEN_2=%3Csz9A&PAGEN_3=%3Csz9B&PAGEN_4=%3Csz9C&PAGEN_5=%3Csz9D&PAGE_NAME=%3Csz9E&PASS=%3Csz9F&PASSWORD=%3CszA0&PBMInit=%3CszA1&PC=%3CszA2&PF=%3CszA3&PG=%3CszA4&PGFLngID=%3CszA5&PG_ID=%3CszA6&PHONE=%3CszA7&PHPSESSID=%3CszA8&PHPSESSIONID=%3CszA9&PID=%3CszAA&PId=%3CszAB&PLanguage=%3CszAC&PN=%3CszAD&PPE_SID=%3CszAE&PR=%3CszAF&PRESET=%3CszB0&PREVIEW=%3CszB1&PRIVILEGES=%3CszB2&PS=%3CszB3&PT=%3CszB4&PUBL=%3CszB5&PUT=%3CszB6&PWD=%3CszB7&PXSId=%3CszB8&PaRes=%3CszB9&Pag=%3CszBA&Page=%3CszBB&PageAction=%3CszBC&PageID=%3CszBD&PageId=%3CszBE&PageIndex=%3CszBF&PageKey=%3CszC0&PageName=%3CszC1&PageNo=%3CszC2&PageNr=%3CszC3&PageNum=%3CszC4&PageNumber=%3CszC5&PageSize=%3CszC6&PageSpeed=%3CszC7&PageType=%3CszC8&Parent=%3CszC9&ParentBoothID=%3CszCA&ParentID=%3CszCB&ParentPage=%3CszCC&Part=%3CszCD&Password=%3CszCE&PasswordForm=%3CszCF&PasswordResetForm=%3CszD0&Path=%3CszD1&PathInfo=%3CszD2&PayPalOrderConfirmation=%3CszD3&PayerID=%3CszD4&PayerStatus=%3CszD5&Perms=%3CszD6&Person=%3CszD7&PersonAccountID=%3CszD8&PersonID=%3CszD9&PersonId=%3CszDA&PetType=%3CszDB&PgID=%3CszDC&PhotoBy=%3CszDD&Pid=%3CszDE&Plain=%3CszDF&PlayerID=%3CszE0&PortalId=%3CszE1&Post=%3CszE2&PostCode=%3CszE3&PostCodeResult=%3CszE4&PostID=%3CszE5&ProdID=%3CszE6

Probably just someone trying to get backend access for any CMS.

Malicious requests like this happen all the time, but could this be handled better in /cms-core/Classes/Routing/PageRouter.php?
Is this a possible log flooding issue?

TYPO3 13.4.31 | PHP 8.2

Reviews 2

History 48

  1. Garvin Hicking commented and changed category status New Needs Feedback <span data-processor="relativetime" data-value="2026-06-22T10:00:45+00:00" > 06/22/26, 10:00 </span>

    Hi!

    Usually this should be caught by cHash validation. Seems you turned off this validation, or added one of the URI parameters contained in this request to be recognized as being valid?

    I cannot reproduce the error in my own setup, so maybe you can try to make a minimal reproducible example on a vanilla installation?

  2. Florian Seirer commented <span data-processor="relativetime" data-value="2026-06-22T15:39:20+00:00" > 06/22/26, 15:39 </span>

    I tried the same parameters on a local demo installation, and TYPO3 gave me the expected 404 error:

    The page did not exist or was inaccessible. Reason: Request parameters could not be validated (&cHash empty)

    These are the excluded parameters on my site:

        'FE' => [
            'cacheHash' => [
                'excludedParameters' => [
                    'utm_source',
                    'utm_medium',
                    'utm_campaign',
                    'authcode',
                    'email',
                ],

    None of them appear in the request.
    I’ll try to isolate the “bad” parameters, but as this only causes some log entries and nothing more, I’d consider it low priority.

  3. Gerrit Code Review pushed patch set 1 for main to change 96302 status Needs Feedback Under Review <span data-processor="relativetime" data-value="2026-10-02T09:03:10+00:00" > 10/02/26, 09:03 </span>

  4. Georg Ringer commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-10-23T15:20:13+00:00" > 10/23/26, 15:20 </span>

    Applied in changeset commit:adaa2aa452c447741cb728cb4e920b0228402b90.

  5. Gerrit Code Review pushed patch set 2 for 14.3 to change 97086 status Resolved Under Review <span data-processor="relativetime" data-value="2026-10-23T21:26:36+00:00" > 10/23/26, 21:26 </span>

  6. Georg Ringer commented and changed status Under Review Resolved <span data-processor="relativetime" data-value="2026-10-25T17:35:14+00:00" > 10/25/26, 17:35 </span>

    Applied in changeset commit:402f034d39ef639f44cbbc8abe9e9ca4814a932d.