How severe is CVE-2018-19789?

CVE-2018-19789 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2018-19789?

CVE-2018-19789 affects the following packages: symfony/symfony (Packagist), symfony/symfony (Packagist), symfony/symfony (Packagist), symfony/symfony (Packagist), symfony/symfony (Packagist), symfony/symfony (Packagist), symfony/form (Packagist), symfony/form (Packagist), and 4 more. Ecosystems affected: Packagist.

How do I fix CVE-2018-19789?

Update symfony/symfony to 2.7.50 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-19789 is resolved across your whole dependency graph.

How do I detect CVE-2018-19789 in my Packagist dependencies?

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

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

Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

Is CVE-2018-19789 actively exploited in the wild?

No public exploit code has been indexed for CVE-2018-19789 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-2018-19789?

CVE-2018-19789 has an EPSS (Exploit Prediction Scoring System) score of 3.6%, placing it in the 89th 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-2018-19789?

CVE-2018-19789 is classified as Unrestricted File Upload (CWE-434). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2018-19789 published, and has it been updated?

CVE-2018-19789 was published on December 18, 2018 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

MEDIUM severity

CVE-2018-19789 — symfony

MEDIUMFix: symfony/symfony@b65e6f1

CVE-2018-19789 is a medium-severity (CVSS 5.3) Unrestricted File Upload vulnerability in symfony/symfony. A fix is available for symfony/symfony — see the affected versions and patch details below.

Symfony Path Disclosure

Also known asGHSA-x3cf-w64x-4cp2

Published

Dec 18, 2018

Updated

Oct 24, 2026

Affected

12 pkgs

Patched

12 / 12

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

3.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs89th percentile — riskier than 89% 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

12 pkgs affected

🐘symfony/symfony🐘symfony/symfony🐘symfony/symfony🐘symfony/symfony🐘symfony/symfony🐘symfony/symfony🐘symfony/form🐘symfony/form+4 more

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 Symfony 2.7.x before 2.7.50, 2.8.x before 2.8.49, 3.x before 3.4.20, 4.0.x before 4.0.15, 4.1.x before 4.1.9, and 4.2.x before 4.2.1. When using the scalar type hint string in a setter method (e.g. setName(string $name)) of a class that's the data_class of a form, and when a file upload is submitted to the corresponding field instead of a normal text input, then UploadedFile::__toString() is called which will then return and disclose the path of the uploaded file. If combined with a local file inclusion issue in certain circumstances this could escalate it to a Remote Code Execution.

Affected Packages

12 total 12 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`symfony/symfony`	≥ 2.7.0&&< 2.7.50	2.7.50`composer require symfony/symfony:^2.7.50`
🐘Packagist	`symfony/symfony`	≥ 2.8.0&&< 2.8.49	2.8.49`composer require symfony/symfony:^2.8.49`
🐘Packagist	`symfony/symfony`	≥ 3.0.0&&< 3.4.20	3.4.20`composer require symfony/symfony:^3.4.20`
🐘Packagist	`symfony/symfony`	≥ 4.0.0&&< 4.0.15	4.0.15`composer require symfony/symfony:^4.0.15`
🐘Packagist	`symfony/symfony`	≥ 4.1.0&&< 4.1.9	4.1.9`composer require symfony/symfony:^4.1.9`
🐘Packagist	`symfony/symfony`	≥ 4.2.0&&< 4.2.1	4.2.1`composer require symfony/symfony:^4.2.1`

Affected Products

2 products · 7 configurations

debian linuxdebian

1 version

8.0

Application

symfonysensiolabs

≥ 4.2.0 && < 4.2.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/symfony, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symfony/symfony to 2.7.50 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-19789 is resolved across your whole dependency graph.
Workarounds
Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

Frequently Asked Questions

An issue was discovered in Symfony 2.7.x before 2.7.50, 2.8.x before 2.8.49, 3.x before 3.4.20, 4.0.x before 4.0.15, 4.1.x before 4.1.9, and 4.2.x before 4.2.1. When using the scalar type hint `string` in a setter method (e.g. `setName(string $name)`) of a class that's the `data_class` of a form, and when a file upload is submitted to the corresponding field instead of a normal text input, then `UploadedFile::__toString()` is called which will then return and disclose the path of the uploaded file. If combined with a local file inclusion issue in certain circumstances this could escalate it to

O3 Security · Impact-Aware SCA

Is CVE-2018-19789 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works