How severe is CVE-2013-1397?

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

Which packages are affected by CVE-2013-1397?

CVE-2013-1397 affects the following packages: symfony/symfony (Packagist), symfony/symfony (Packagist), symfony/symfony (Packagist), symfony/yaml (Packagist), symfony/yaml (Packagist), symfony/yaml (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2013-1397?

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

How do I detect CVE-2013-1397 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-2013-1397 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2013-1397 actively exploited in the wild?

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

CVE-2013-1397 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 76th 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-2013-1397?

CVE-2013-1397 is classified as Code Injection (CWE-94). 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-2013-1397 published, and has it been updated?

CVE-2013-1397 was published on May 17, 2022 and was last updated on April 14, 2025. 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-2013-1397 — symfony

Fix: symfony/symfony@ba6e315

CVE-2013-1397 is a Code Injection vulnerability in symfony/symfony. A fix is available for symfony/symfony — see the affected versions and patch details below.

Symfony Arbitrary PHP code Execution

Published

May 17, 2022

Updated

Apr 14, 2025

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs76th percentile — riskier than 76% of all scored CVEsHighest risk

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

Real-World Exposure

6 pkgs affected

🐘symfony/symfony🐘symfony/symfony🐘symfony/symfony🐘symfony/yaml🐘symfony/yaml🐘symfony/yaml

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

Symfony 2.0.x before 2.0.22, 2.1.x before 2.1.7, and 2.2.x remote attackers to execute arbitrary PHP code via a serialized PHP object to the (1) Yaml::parse or (2) Yaml\Parser::parse function, a different vulnerability than CVE-2013-1348.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`symfony/symfony`	≥ 2.2.0-BETA1&&< 2.2.0-BETA2	2.2.0-BETA2`composer require symfony/symfony:^2.2.0-BETA2`
🐘Packagist	`symfony/symfony`	≥ 2.0.0&&< 2.0.22	2.0.22`composer require symfony/symfony:^2.0.22`
🐘Packagist	`symfony/symfony`	≥ 2.1.0&&< 2.1.7	2.1.7`composer require symfony/symfony:^2.1.7`
🐘Packagist	`symfony/yaml`	≥ 2.0.0&&< 2.0.22	2.0.22`composer require symfony/yaml:^2.0.22`
🐘Packagist	`symfony/yaml`	≥ 2.1.0&&< 2.1.7	2.1.7`composer require symfony/yaml:^2.1.7`
🐘Packagist	`symfony/yaml`	≥ 2.2.0-BETA1&&< 2.2.0-BETA2	2.2.0-BETA2`composer require symfony/yaml:^2.2.0-BETA2`

Affected Products

1 product · 40 configurations

Application

symfonysensiolabs

40 versions

2.0.02.0.12.0.22.0.32.0.42.0.52.0.62.0.72.0.82.0.92.0.102.0.11

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.2.0-BETA2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-1397 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-1397 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works