Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8

TYPO3 Arbitrary Code Execution

CVE-2017-14251GHSA-fh4q-hxrw-cjqq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms 8.7.5, 7.6.22), 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
    >= 7.6.0, < 7.6.22>= 8.0.0, < 8.7.5
    Fixed in
    7.6.22, 8.7.5

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2017-14251: 2.31% estimated exploitation activity in the next 30 days; percentile 83.41 (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.

Unrestricted File Upload vulnerability in the fileDenyPattern in sysext/core/Classes/Core/SystemEnvironmentBuilder.php in TYPO3 7.6.0 to 7.6.21 and 8.0.0 to 8.7.4 allows remote authenticated users to upload files with a .pht extension and consequently execute arbitrary PHP code.

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

    Published from ghsa record GHSA-fh4q-hxrw-cjqq

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-2017-14251

Advisory: TYPO3 Arbitrary Code Execution
IDs: CVE-2017-14251, GHSA-fh4q-hxrw-cjqq
Record: https://patchnext.com/advisories/cve-2017-14251 (revision 1, source checked 26 Oct 2026, 14:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms 8.7.5, 7.6.22. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms: affected >= 7.6.0, < 7.6.22; >= 8.0.0, < 8.7.5; fixed in 7.6.22, 8.7.5

## 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-fh4q-hxrw-cjqq (GitHub-reviewed advisory GHSA-fh4q-hxrw-cjqq lists affected ranges: Packagist typo3/cms >=7.6.0 =8.0.0 <8.7.5)

Commands are suggestions: review each one before running it.

Loading voting…