How severe is CVE-2019-19848?

CVE-2019-19848 has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-19848?

CVE-2019-19848 affects the following packages: typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms (Packagist), typo3/cms (Packagist), typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2019-19848?

Update typo3/cms-core to 10.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-19848 is resolved across your whole dependency graph.

How do I detect CVE-2019-19848 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-19848 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2019-19848 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-19848 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-19848?

CVE-2019-19848 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 73th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-19848?

CVE-2019-19848 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2019-19848 published, and has it been updated?

CVE-2019-19848 was published on December 17, 2019 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

CVE-2019-19848 — cms-core

HIGH

CVE-2019-19848 is a high-severity (CVSS 7.2) Path Traversal vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.

TYPO3 Directory Traversal on ZIP extraction

Also known asGHSA-77p4-wfr8-977w

Published

Dec 17, 2019

Updated

Oct 24, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

6 pkgs affected

🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms🐘typo3/cms🐘typo3/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

An issue was discovered in TYPO3 before 8.7.30, 9.x before 9.5.12, and 10.x before 10.2.2. It has been discovered that the extraction of manually uploaded ZIP archives in Extension Manager is vulnerable to directory traversal. Admin privileges are required in order to exploit this vulnerability. (In v9 LTS and later, System Maintainer privileges are also required.)

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-core`	≥ 10.0.0&&< 10.2.2	10.2.2`composer require typo3/cms-core:^10.2.2`
🐘Packagist	`typo3/cms-core`	≥ 8.0.0&&< 8.7.30	8.7.30`composer require typo3/cms-core:^8.7.30`
🐘Packagist	`typo3/cms-core`	≥ 9.0.0&&< 9.5.12	9.5.12`composer require typo3/cms-core:^9.5.12`
🐘Packagist	`typo3/cms`	≥ 10.0.0&&< 10.2.2	10.2.2`composer require typo3/cms:^10.2.2`
🐘Packagist	`typo3/cms`	≥ 8.0.0&&< 8.7.30	8.7.30`composer require typo3/cms:^8.7.30`
🐘Packagist	`typo3/cms`	≥ 9.0.0&&< 9.5.12	9.5.12`composer require typo3/cms:^9.5.12`

Affected Products

1 product · 3 configurations

Application

typo3typo3

≥ 10.0.0 && < 10.2.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-core to 10.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-19848 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-19848 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.2/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-22Path Traversal

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

security-advisories

4.8/10

Maintained10/10

Code-Review10/10

Branch-Protection0/10

Assessed Nov 2, 2026

Timeline

Disclosed

Dec 17, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2019-19848

GHSA-77p4-wfr8-977w

References

Advisoryreview.typo3.org · %22Resolves:+%2388764%22+topic:security Advisorytypo3.org · typo3 core sa 2019 024 Advisorynvd.nist.gov · CVE 2019 19848 Webgithub.com · CVE 2019 19848.yaml Webgithub.com · CVE 2019 19848.yaml Webtypo3.org · typo3 core sa 2019 024

Related vulnerabilities

This CVE is high severity; 3 of 8 other CVEs affecting typo3/cms-core are rated as high or higher (top: high).

CVE-2026-19418CVE-2026-47352CVE-2026-47347CVE-2026-47343CVE-2026-49740CVE-2026-47348CVE-2026-49742CVE-2026-47349

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2019-19848 — cms-core

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2019-19848 in your dependencies?