Issue Task Rejected

#109036Clear password visible in the phpinfo

Ludovic Nogueira 02/20/26, 10:46 updated 02/20/26, 19:01

Description

Hello,

So, TYPO3 is hiding the db credentials inside the “Configuration” module, which is great
!clipboard-202602201146-uosft.png!
But, as advised here https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Administration/Deployment/EnvironmentStages/Configuration/Index.html, we use .env file for our environments. Which result in the password being shown inside phpinfo inside environment module
!clipboard-202602201145-jsjhj.png!
Which makes hiding them inside configuration module pointless.

TYPO3 should at the very least hide everything that can be considered a password inside the phpinfo.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Files 2

History 4

  1. Georg Ringer commented and changed status New Rejected <span data-processor="relativetime" data-value="2026-02-20T16:52:19+00:00" > 02/20/26, 16:52 </span>

    Thanks for creating this issue!
    As the phpinfo is a function of php itself and only visible to system maintainers, there is nothing TYPO3 can do!
    If phpinfo is problematic for you, you could use

    disable_functions = phpinfo
  2. Ludovic Nogueira commented <span data-processor="relativetime" data-value="2026-02-20T17:44:04+00:00" > 02/20/26, 17:44 </span>

    The same goes for the configuration module, it’s only accessible for system maintainers, but there, the password is hidden.

    So if we follow the doc and use .env, TYPO3 will hide the DB password in configuration, but it’ll be accessible with the phpinfo. It’s a bit counterintuitive and make the blinded options totally pointless. Also, totally hidding the phpinfo module is not an option for us.

    I understand that the .env is up to the user, but there should at least be a mention in the doc to warn user about this issue.

    For this issue, I’ll just override or git patch it and make a regex that lookup for password keyword and hide the value.

  3. Garvin Hicking commented <span data-processor="relativetime" data-value="2026-02-20T18:48:31+00:00" > 02/20/26, 18:48 </span>

    The docs should actually only show that using ENV variables are one way of many to manage credentials. So this is not the only option you have, and it is certainly not required.

    In the Configuration Module, TYPO3 knows EXACTLY which values we can blend. But with ENV, we have no allow/blocklist, so we cannot infer which values are what.

    Some people call it “TYPO3_PASSWORD”, others “PASS_TYPO3” and others maybe “MY_CMS_CREDENTIAL”. We will not know what to block.

    Another way would be to completely block ENV output in the TYPO3 most inner low level admin access, but then other admins might be annoyed to no longer have that information.

    Maybe you can contribute a docs patch or create an issue that there should be information about possible exposure of ENV variables in PHPinfo. That would be nice, because I agree, there should be information about it.

  4. Ludovic Nogueira commented <span data-processor="relativetime" data-value="2026-02-20T19:01:36+00:00" > 02/20/26, 19:01 </span>

    Maybe an option to disable some phpinfo flags?

    https://www.php.net/manual/en/function.phpinfo.php

    Like in our case if we block INFO_ENVIRONMENT + INFO_VARIABLES it would do the trick.

    Will see for a potential doc patch or something else next week.