TYPO3CMS
CVE-2005-4875
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTYPO3 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceTYPO3 CMS versions 3.8.0 and earlier contain a direct request vulnerability in the misc/phpcheck/ directory that invokes the phpinfo() function, exposing sensitive server configuration details, environment variables, PHP settings, and path information to remote attackers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
TYPO3CMS
<= 3.8.0= 1.1= 3.7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed TYPO3 versionLocate the version file in your TYPO3 installation (typically in t3lib/ or typo3/sysext/core/ directory, or check the release notes file). Run: grep -r 'TYPO3_VERSION' or find . -name 'Version*.php' 2>/dev/null | head -5Affected if The installed version is 3.8.0 or earlier, or specifically 1.1 or 3.7.0
-
Check for misc/phpcheck directory existenceList the misc/ subdirectory in your web root. Run: ls -la path/to/typo3/misc/ or find . -type d -name 'phpcheck' 2>/dev/nullAffected if The misc/phpcheck/ directory exists in the TYPO3 installation
-
Verify phpinfo exposure via web requestAttempt an HTTP request to the suspected path. Run: curl -s http://yourdomain.com/misc/phpcheck/ or wget -q -O- http://yourdomain.com/misc/phpcheck/ 2>/dev/nullAffected if The request returns PHP configuration output including version, settings, loaded extensions, or server environment variables
-
Confirm directory is web-accessibleReview web server configuration (Apache .htaccess, nginx config, or IIS URL authorization rules) to verify the misc/phpcheck/ directory is not explicitly denied or removedAffected if The directory exists and web server configuration allows access to it
You are affected if your TYPO3 version is 3.8.0 or earlier (including 1.1 or 3.7.0) AND the misc/phpcheck/ directory exists and is accessible via web requests, causing phpinfo() output to be exposed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemove or disable the misc/phpcheck/ directory entirely, or configure web server access controls to deny requests to this path. Consider upgrading to a supported TYPO3 version if not already done.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-4875 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2005-4875 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data