Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

TYPO3 Reveals Sensitive Information via Direct Request to misc/phpcheck/

CVE-2005-4875GHSA-xj84-6q8f-qg2r

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms 3.8.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist typo3/cms

    Affected
    < 3.8.1
    Fixed in
    3.8.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2005-4875: 1.38% estimated exploitation activity in the next 30 days; percentile 72.18 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

TYPO3 3.8.0 and earlier allows remote attackers to obtain sensitive information via a direct request to misc/phpcheck/, which invokes the phpinfo function and prints values of unspecified environment variables.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-xj84-6q8f-qg2r

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2005-4875

Advisory: TYPO3 Reveals Sensitive Information via Direct Request to `misc/phpcheck/`
IDs: CVE-2005-4875, GHSA-xj84-6q8f-qg2r
Record: https://patchnext.com/advisories/cve-2005-4875 (revision 1, source checked 26 Oct 2026, 14:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms 3.8.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms: affected < 3.8.1; fixed in 3.8.1

## Suggested inspection (read-only)
- Packagist typo3/cms: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typo3/cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xj84-6q8f-qg2r (GitHub-reviewed advisory GHSA-xj84-6q8f-qg2r lists affected ranges: Packagist typo3/cms >=0 <3.8.1)

Commands are suggestions: review each one before running it.

Loading voting…