adam/Piwigo
1
0 Fork 0
mirror of https://github.com/Piwigo/Piwigo.git synced 2026-11-03 07:22:22 +01:00
Code Issues 657 Packages Projects Releases Wiki Activity

Piwigo spits out db pw if php-mysqli is missing #678

New Issue
Open
opened 2026-10-05 00:11:09 +02:00 by adam · 1 comment
adam commented 2026-10-05 00:11:09 +02:00
Owner
Copy link
Copy source

Hi there,

Yesterday i moved piwigo to a new host. on this host, php-mysqli was missing. As i called the url of gallery, i got an error message including my database password. I anonymized paths, usernames, ip-adress and of course the password for this report.

Fatal error: Uncaught Error: Class 'mysqli' not found in /export/home/foo/bar/piwigo/include/dblayer/functions_mysqli.inc.php:67
Stack trace: #0 /export/home/foo/bar/piwigo/include/common.inc.php(124): pwg_db_connect('ip-adress', 'foo', 'password', 'foo')
#1 /export/home/foo/bar/piwigo/index.php(26): include_once('/export/home/sm...')
#2 {main} thrown in /export/home/foo/bar/piwigo/include/dblayer/functions_mysqli.inc.php on line 67

Hi there, Yesterday i moved piwigo to a new host. on this host, php-mysqli was missing. As i called the url of gallery, i got an error message including my database password. I anonymized paths, usernames, ip-adress and of course the password for this report. Fatal error: Uncaught Error: Class 'mysqli' not found in /export/home/foo/bar/piwigo/include/dblayer/functions_mysqli.inc.php:67 Stack trace: #0 /export/home/foo/bar/piwigo/include/common.inc.php(124): pwg_db_connect('ip-adress', 'foo', 'password', 'foo') #1 /export/home/foo/bar/piwigo/index.php(26): include_once('/export/home/sm...') #2 {main} thrown in /export/home/foo/bar/piwigo/include/dblayer/functions_mysqli.inc.php on line 67 <!-- github-sync-id:243228662 -->
adam commented 2026-10-05 00:11:10 +02:00
Author
Owner
Copy link
Copy source

I'm not too certain this is a Piwigo issue as much as it would be your PHP configuration.. Ideally you would not be delivering stack traces for exceptions to your clients; store that server-side in your php logs (were obviously if someone has access to them they could just as easily access your config file for piwigo anyway).

However it does seem like maybe an ini_set('display_errors', 0) in that common.inc.php file would be a reasonable measure to prevent this kind of thing.

I'm not too certain this is a Piwigo issue as much as it would be your PHP configuration.. Ideally you would not be delivering stack traces for exceptions to your clients; store that server-side in your php logs (were obviously if someone has access to them they could just as easily access your config file for piwigo anyway). However it does seem like maybe an `ini_set('display_errors', 0)` in that `common.inc.php` file would be a reasonable measure to prevent this kind of thing. <!-- github-comment-id:321052081 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Piwigo#678