How severe is CVE-2017-20187?

CVE-2017-20187 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-20187?

CVE-2017-20187 affects the following packages: floriangaerber/magnesium (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2017-20187?

Update floriangaerber/magnesium to 0.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-20187 is resolved across your whole dependency graph.

How do I detect CVE-2017-20187 in my Packagist dependencies?

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2017-20187 actively exploited in the wild?

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

CVE-2017-20187 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 58th 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-2017-20187?

CVE-2017-20187 is classified as CWE-74 (CWE-74). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-20187 published, and has it been updated?

CVE-2017-20187 was published on November 5, 2023 and was last updated on October 20, 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

CRITICAL severity

CVE-2017-20187 — magnesium

CRITICALFix: floriangaerber/Magnesium-PHP@500d340

CVE-2017-20187 is a critical-severity (CVSS 9.8) CWE-74 vulnerability in floriangaerber/magnesium. A fix is available for floriangaerber/magnesium — see the affected versions and patch details below.

Magnesium-PHP Injection vulnerability

Also known asGHSA-8pp6-5qpw-85g3

Published

Nov 5, 2023

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2017-20187.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk+0.15%

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

1 pkg affected

🐘floriangaerber/magnesium

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

** UNSUPPORTED WHEN ASSIGNED ** ** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in Magnesium-PHP up to 0.3.0. It has been classified as problematic. Affected is the function formatEmailString of the file src/Magnesium/Message/Base.php. The manipulation of the argument email/name leads to injection. Upgrading to version 0.3.1 is able to address this issue. The patch is identified as 500d340e1f6421007413cc08a8383475221c2604. It is recommended to upgrade the affected component. VDB-244482 is the identifier assigned to this vulnerability. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`floriangaerber/magnesium`	all versions	0.3.1`composer require floriangaerber/magnesium:^0.3.1`

Affected Products

1 product · 1 configurations

Application

magnesium-phpfloriangaerber

≤ 0.3.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for floriangaerber/magnesium, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update floriangaerber/magnesium to 0.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-20187 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

** UNSUPPORTED WHEN ASSIGNED ** ** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in Magnesium-PHP up to 0.3.0. It has been classified as problematic. Affected is the function formatEmailString of the file `src/Magnesium/Message/Base.php`. The manipulation of the argument email/name leads to injection. Upgrading to version 0.3.1 is able to address this issue. The patch is identified as 500d340e1f6421007413cc08a8383475221c2604. It is recommended to upgrade the affected component. VDB-244482 is the identifier assigned to this vulnerability. NOTE: This vulnerability only affects products

O3 Security · Impact-Aware SCA

Is CVE-2017-20187 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-74CWE-74

Weaponization

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

Timeline

Disclosed

Nov 5, 2023

Last updated

Oct 20, 2026

Identifiers

CVE-2017-20187

GHSA-8pp6-5qpw-85g3

References

Advisorygithub.com · v0.3.1 Advisoryvuldb.com Advisoryvuldb.com Advisorynvd.nist.gov · CVE 2017 20187 Fixgithub.com · 500d340e1f6421007413cc08a8383475221c2604 Packagegithub.com · Magnesium PHP

Related vulnerabilities

This CVE is critical severity; 1 of 8 other CVEs with CWE-74 is rated as high or higher (top: critical).

CVE-2026-96634CVE-2026-118258CVE-2026-115730CVE-2026-105800CVE-2026-101900CVE-2026-101904CVE-2026-61732GHSA-wwv5-g3v4-889xBrowse all CWE-74

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2017-20187 — magnesium

Exploitation Status

No confirmed exploitation observed yet

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-2017-20187 in your dependencies?