bad chronology field (date) for invalid input #2151

Open
opened 2026-10-05 01:07:59 +02:00 by adam · 0 comments
Owner

I noticed several errors in my PHP logs, e.g.,

[03-Dec-2025 21:02:31 UTC] PHP Deprecated: Passing E_USER_ERROR to trigger_error() is deprecated since 8.4, throw an exception or call exit with a string message instead in /home/xxx/public_html/gallery/include/functions_html.inc.php on line 384
[03-Dec-2025 21:02:31 UTC] PHP Fatal error: bad chronology field (date)
#1 parse_well_known_params_url /home/xxx/public_html/gallery/include/section_init.inc.php(154)
#2 include /home/xxx/public_html/gallery/index.php(12) in /home/xxx/public_html/gallery/include/functions_html.inc.php on line 384
Stack trace:
#0 /home/xxx/public_html/gallery/include/functions_html.inc.php(384): trigger_error('bad chronology ...', 256)
#1 /home/xxx/public_html/gallery/include/functions_url.inc.php(737): fatal_error('bad chronology ...')
#2 /home/xxx/public_html/gallery/include/section_init.inc.php(154): parse_well_known_params_url(Array, 0)
#3 /home/xxx/public_html/gallery/index.php(12): include('/home/xxx/public...')
#4 {main}

Looks like these are triggered by some bots, likely looking for directory traversal, corresponding request is this:

x.x.x.x- - [03/Dec/2025:22:02:31 +0100] "GET /gallery/index/created-monthly-list-2022-06-03../_data/i/upload/2022/06/05/20220605160625-0fd8480c-sm.jpg HTTP/1.1" 500 754 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0"

Now, because of the ".." after 2022-06-03. Piwigo borks with

"Piwigo encountered an unrecoverable problem.
bad chronology field (date)

#1 parse_well_known_params_url /home/xxx/public_html/gallery/include/section_init.inc.php(154)
#2 include /home/xxx/public_html/gallery/index.php(12)"

I'm able to reproduce this on some sites on piwigo.com I looked at, e.g.,
https://[xxx].piwigo.com/picture?/xxxxx/categories/created-monthly-calendar-2025-2-3..

I noticed several errors in my PHP logs, e.g., [03-Dec-2025 21:02:31 UTC] PHP Deprecated: Passing E_USER_ERROR to trigger_error() is deprecated since 8.4, throw an exception or call exit with a string message instead in /home/xxx/public_html/gallery/include/functions_html.inc.php on line 384 [03-Dec-2025 21:02:31 UTC] PHP Fatal error: bad chronology field (date) #1 parse_well_known_params_url /home/xxx/public_html/gallery/include/section_init.inc.php(154) #2 include /home/xxx/public_html/gallery/index.php(12) in /home/xxx/public_html/gallery/include/functions_html.inc.php on line 384 Stack trace: #0 /home/xxx/public_html/gallery/include/functions_html.inc.php(384): trigger_error('bad chronology ...', 256) #1 /home/xxx/public_html/gallery/include/functions_url.inc.php(737): fatal_error('bad chronology ...') #2 /home/xxx/public_html/gallery/include/section_init.inc.php(154): parse_well_known_params_url(Array, 0) #3 /home/xxx/public_html/gallery/index.php(12): include('/home/xxx/public...') #4 {main} Looks like these are triggered by some bots, likely looking for directory traversal, corresponding request is this: x.x.x.x- - [03/Dec/2025:22:02:31 +0100] "GET /gallery/index/created-monthly-list-2022-06-03../_data/i/upload/2022/06/05/20220605160625-0fd8480c-sm.jpg HTTP/1.1" 500 754 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0" Now, because of the ".." after 2022-06-03. Piwigo borks with "Piwigo encountered an unrecoverable problem. bad chronology field (date) #1 parse_well_known_params_url /home/xxx/public_html/gallery/include/section_init.inc.php(154) #2 include /home/xxx/public_html/gallery/index.php(12)" I'm able to reproduce this on some sites on piwigo.com I looked at, e.g., https://[xxx].piwigo.com/picture?/xxxxx/categories/created-monthly-calendar-2025-2-3.. <!-- github-sync-id:3699753230 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Piwigo#2151