How severe is CVE-2024-58303?

No CVSS score has been assigned to CVE-2024-58303 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-58303?

CVE-2024-58303 affects the following packages: fof/pretty-mail (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2024-58303?

The records we use list no patched version of fof/pretty-mail for CVE-2024-58303. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2024-58303 in my Packagist dependencies?

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

How do I mitigate CVE-2024-58303 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-2024-58303 actively exploited in the wild?

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

CVE-2024-58303 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 45th 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-2024-58303?

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

When was CVE-2024-58303 published, and has it been updated?

CVE-2024-58303 was published on December 11, 2025 and was last updated on October 28, 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

CVE-2024-58303 — pretty-mail

CVE-2024-58303 is a CWE-1336 vulnerability in fof/pretty-mail. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

FoF Pretty Mail 1.1.2 Server Side Template Injection via Email Template Settings

Also known asGHSA-947q-2xw3-gx9c

Published

Dec 11, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-2024-58303.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs45th percentile — riskier than 45% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐘fof/pretty-mail

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

FoF Pretty Mail 1.1.2 contains a server-side template injection vulnerability that allows administrative users to inject malicious code into email templates. Attackers can execute system commands by inserting crafted template expressions that trigger arbitrary code execution during email generation.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`fof/pretty-mail`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fof/pretty-mail, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of fof/pretty-mail for CVE-2024-58303. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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

O3 Security · Impact-Aware SCA

Is CVE-2024-58303 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works