What is CVE-2013-1348?

CVE-2013-1348 is a high-severity code injection vulnerability in symfony/symfony (composer), affecting versions >= 2.0.0, < 2.0.22. It is fixed in 2.0.22. Untrusted input is evaluated as executable code within the application's runtime environment.

Which packages are affected by CVE-2013-1348?

symfony/symfony (composer) versions >= 2.0.0, = 2.0.0, < 2.0.22.

Is there a fix for CVE-2013-1348?

Yes. CVE-2013-1348 is fixed in 2.0.22. Upgrade to this version or later.

Is CVE-2013-1348 exploitable, and should I be worried?

Whether CVE-2013-1348 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2013-1348 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2013-1348 in symfony/symfony

Q: Which packages are affected by CVE-2013-1348?

symfony/symfony (composer) versions >= 2.0.0, = 2.0.0, < 2.0.22.

Q: Is there a fix for CVE-2013-1348?

Yes. CVE-2013-1348 is fixed in 2.0.22. Upgrade to this version or later.

Q: Is CVE-2013-1348 exploitable, and should I be worried?

Whether CVE-2013-1348 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2013-1348 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2013-1348?

Upgrade: symfony/symfony to 2.0.22 or later, symfony/yaml to 2.0.22 or later.

Summary

Symphony Vulnerable to PHP Code Injection via YAML Parsing

The Yaml::parse function in Symfony 2.0.x before 2.0.22 remote attackers to execute arbitrary PHP code via a PHP file, a different vulnerability than CVE-2013-1397.

Impact

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

Affected versions

symfony/symfony (>= 2.0.0, < 2.0.22) symfony/yaml (>= 2.0.0, < 2.0.22)

Security releases

symfony/symfony → 2.0.22 (composer) symfony/yaml → 2.0.22 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

symfony/symfony to 2.0.22 or later; symfony/yaml to 2.0.22 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2013-1348? CVE-2013-1348 is a high-severity code injection vulnerability in symfony/symfony (composer), affecting versions >= 2.0.0, < 2.0.22. It is fixed in 2.0.22. Untrusted input is evaluated as executable code within the application's runtime environment.
Which packages are affected by CVE-2013-1348?
- symfony/symfony (composer) (versions >= 2.0.0, < 2.0.22)
- symfony/yaml (composer) (versions >= 2.0.0, < 2.0.22)
Is there a fix for CVE-2013-1348? Yes. CVE-2013-1348 is fixed in 2.0.22. Upgrade to this version or later.
Is CVE-2013-1348 exploitable, and should I be worried? Whether CVE-2013-1348 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2013-1348 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2013-1348?
- Upgrade symfony/symfony to 2.0.22 or later
- Upgrade symfony/yaml to 2.0.22 or later

Other vulnerabilities in symfony/symfony

CVE-IDSeverityPackage summary

CVE-2026-48784Mediumsymfony/routing: Symfony: UrlGenerator Dot-Segment Encoding Skips Every Other Chained `../` or `./` → Generated URL Collapses Off-Route Under RFC 3986…CVE-2026-48760Mediumsymfony/html-sanitizer: Symfony: HtmlSanitizer URL Parser Deny Gates Underinclusive: Percent-Encoded BiDi Marks and Unicode Whitespace Bypass Visual-Spoofing…CVE-2026-48747Mediumsymfony/mailomat-mailer: Symfony: Mailomat Mailer Webhook Parser Reads the HMAC Algorithm from the Request: Signature Algorithm Downgrade CVE-2026-48736Mediumsymfony/http-client: Symfony: IpUtils::PRIVATE_SUBNETS Omits IPv6 Transition Forms (6to4, NAT64, Teredo, IPv4-compatible): SSRF Bypass in…CVE-2026-48489Highsymfony/security-http: Symfony: Security Firewall Bypass via failure_forward Subrequest: Unauthenticated Access to access_control-Protected GET Routes