{"items":[{"id":"NVI-00007083","kind":"vulnerability","title":"Symfony Cross-Site Request Forgery vulnerability in the Web Profiler","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-v35g-4rrw-h4fw","CVE-2014-6072"],"plain_summary":"OSV carries this publisher advisory for symfony/symfony, symfony/symfony, symfony/symfony, symfony/web-profiler-bundle, symfony/web-profiler-bundle. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.3.19 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-cdfa40ea9a660c46cd6217a1eae9e1fa"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.4.9 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-cdfa40ea9a660c46cd6217a1eae9e1fa"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.5.4 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-cdfa40ea9a660c46cd6217a1eae9e1fa"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.3.19 for symfony/web-profiler-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-cdfa40ea9a660c46cd6217a1eae9e1fa"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.4.9 for symfony/web-profiler-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-cdfa40ea9a660c46cd6217a1eae9e1fa"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.5.4 for symfony/web-profiler-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-cdfa40ea9a660c46cd6217a1eae9e1fa"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-cdfa40ea9a660c46cd6217a1eae9e1fa","url":"https://github.com/advisories/GHSA-v35g-4rrw-h4fw","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-v35g-4rrw-h4fw","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.369Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-cdfa40ea9a660c46cd6217a1eae9e1fa"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"All 2.0.X, 2.1.X, 2.2.X, 2.3.X, 2.4.X, and 2.5.X versions of the Symfony WebProfiler bundle are affected by this security issue.\n\nThis issue has been fixed in Symfony 2.3.19, 2.4.9, and 2.5.4. Note that no fixes are provided for Symfony 2.0, 2.1, and 2.2 as they are not maintained anymore.\n\n### Description\nThe Symfony Web Profiler is a great development tool, but it should not be enabled on production servers. If it is enabled in production, it must be properly secured so that only authorized people have access to it. Developers must be very cautious about this as the Web Profiler gives many sensitive information about a Symfony project and any attackers can exploit many of them. Just to name a few sensitive information: user logins, user cookies, executed SQL statements, ...\n\nThat being said, the import/export feature of the web profiler is exploitable even if the Web Profiler is secured as the form to import a profiler is not protected against CSRF attacks. Combined with the fact that profiles are imported as a PHP serialized string, it makes your application vulnerable to code injection.\n\n### Resolution\nAs the import/export feature of the Web Profiler is not that useful, and bec","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.3.19"]},{"certainty":"source_listed","source_ids":["sr-cdfa40ea9a660c46cd6217a1eae9e1fa"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"All 2.0.X, 2.1.X, 2.2.X, 2.3.X, 2.4.X, and 2.5.X versions of the Symfony WebProfiler bundle are affected by this security issue.\n\nThis issue has been fixed in Symfony 2.3.19, 2.4.9, and 2.5.4. Note that no fixes are provided for Symfony 2.0, 2.1, and 2.2 as they are not maintained anymore.\n\n### Description\nThe Symfony Web Profiler is a great development tool, but it should not be enabled on production servers. If it is enabled in production, it must be properly secured so that only authorized people have access to it. Developers must be very cautious about this as the Web Profiler gives many sensitive information about a Symfony project and any attackers can exploit many of them. Just to name a few sensitive information: user logins, user cookies, executed SQL statements, ...\n\nThat being said, the import/export feature of the web profiler is exploitable even if the Web Profiler is secured as the form to import a profiler is not protected against CSRF attacks. Combined with the fact that profiles are imported as a PHP serialized string, it makes your application vulnerable to code injection.\n\n### Resolution\nAs the import/export feature of the Web Profiler is not that useful, and bec","public_affected_ranges":["ECOSYSTEM: introduced 2.4.0; fixed 2.4.9"]},{"certainty":"source_listed","source_ids":["sr-cdfa40ea9a660c46cd6217a1eae9e1fa"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"All 2.0.X, 2.1.X, 2.2.X, 2.3.X, 2.4.X, and 2.5.X versions of the Symfony WebProfiler bundle are affected by this security issue.\n\nThis issue has been fixed in Symfony 2.3.19, 2.4.9, and 2.5.4. Note that no fixes are provided for Symfony 2.0, 2.1, and 2.2 as they are not maintained anymore.\n\n### Description\nThe Symfony Web Profiler is a great development tool, but it should not be enabled on production servers. If it is enabled in production, it must be properly secured so that only authorized people have access to it. Developers must be very cautious about this as the Web Profiler gives many sensitive information about a Symfony project and any attackers can exploit many of them. Just to name a few sensitive information: user logins, user cookies, executed SQL statements, ...\n\nThat being said, the import/export feature of the web profiler is exploitable even if the Web Profiler is secured as the form to import a profiler is not protected against CSRF attacks. Combined with the fact that profiles are imported as a PHP serialized string, it makes your application vulnerable to code injection.\n\n### Resolution\nAs the import/export feature of the Web Profiler is not that useful, and bec","public_affected_ranges":["ECOSYSTEM: introduced 2.5.0; fixed 2.5.4"]},{"certainty":"source_listed","source_ids":["sr-cdfa40ea9a660c46cd6217a1eae9e1fa"],"technology":"symfony/web-profiler-bundle","known_exclusions":[],"conditions_summary":"All 2.0.X, 2.1.X, 2.2.X, 2.3.X, 2.4.X, and 2.5.X versions of the Symfony WebProfiler bundle are affected by this security issue.\n\nThis issue has been fixed in Symfony 2.3.19, 2.4.9, and 2.5.4. Note that no fixes are provided for Symfony 2.0, 2.1, and 2.2 as they are not maintained anymore.\n\n### Description\nThe Symfony Web Profiler is a great development tool, but it should not be enabled on production servers. If it is enabled in production, it must be properly secured so that only authorized people have access to it. Developers must be very cautious about this as the Web Profiler gives many sensitive information about a Symfony project and any attackers can exploit many of them. Just to name a few sensitive information: user logins, user cookies, executed SQL statements, ...\n\nThat being said, the import/export feature of the web profiler is exploitable even if the Web Profiler is secured as the form to import a profiler is not protected against CSRF attacks. Combined with the fact that profiles are imported as a PHP serialized string, it makes your application vulnerable to code injection.\n\n### Resolution\nAs the import/export feature of the Web Profiler is not that useful, and bec","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.3.19"]},{"certainty":"source_listed","source_ids":["sr-cdfa40ea9a660c46cd6217a1eae9e1fa"],"technology":"symfony/web-profiler-bundle","known_exclusions":[],"conditions_summary":"All 2.0.X, 2.1.X, 2.2.X, 2.3.X, 2.4.X, and 2.5.X versions of the Symfony WebProfiler bundle are affected by this security issue.\n\nThis issue has been fixed in Symfony 2.3.19, 2.4.9, and 2.5.4. Note that no fixes are provided for Symfony 2.0, 2.1, and 2.2 as they are not maintained anymore.\n\n### Description\nThe Symfony Web Profiler is a great development tool, but it should not be enabled on production servers. If it is enabled in production, it must be properly secured so that only authorized people have access to it. Developers must be very cautious about this as the Web Profiler gives many sensitive information about a Symfony project and any attackers can exploit many of them. Just to name a few sensitive information: user logins, user cookies, executed SQL statements, ...\n\nThat being said, the import/export feature of the web profiler is exploitable even if the Web Profiler is secured as the form to import a profiler is not protected against CSRF attacks. Combined with the fact that profiles are imported as a PHP serialized string, it makes your application vulnerable to code injection.\n\n### Resolution\nAs the import/export feature of the Web Profiler is not that useful, and bec","public_affected_ranges":["ECOSYSTEM: introduced 2.4.0; fixed 2.4.9"]},{"certainty":"source_listed","source_ids":["sr-cdfa40ea9a660c46cd6217a1eae9e1fa"],"technology":"symfony/web-profiler-bundle","known_exclusions":[],"conditions_summary":"All 2.0.X, 2.1.X, 2.2.X, 2.3.X, 2.4.X, and 2.5.X versions of the Symfony WebProfiler bundle are affected by this security issue.\n\nThis issue has been fixed in Symfony 2.3.19, 2.4.9, and 2.5.4. Note that no fixes are provided for Symfony 2.0, 2.1, and 2.2 as they are not maintained anymore.\n\n### Description\nThe Symfony Web Profiler is a great development tool, but it should not be enabled on production servers. If it is enabled in production, it must be properly secured so that only authorized people have access to it. Developers must be very cautious about this as the Web Profiler gives many sensitive information about a Symfony project and any attackers can exploit many of them. Just to name a few sensitive information: user logins, user cookies, executed SQL statements, ...\n\nThat being said, the import/export feature of the web profiler is exploitable even if the Web Profiler is secured as the form to import a profiler is not protected against CSRF attacks. Combined with the fact that profiles are imported as a PHP serialized string, it makes your application vulnerable to code injection.\n\n### Resolution\nAs the import/export feature of the Web Profiler is not that useful, and bec","public_affected_ranges":["ECOSYSTEM: introduced 2.5.0; fixed 2.5.4"]}],"null_published_at":"2026-10-31T22:13:14.311Z","source_updated_at":"2024-05-30T13:41:54.836Z","source_disclosed_at":"2024-05-30T13:00:01.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:41.369Z"}],"next_cursor":null,"snapshot_revision":"42594"}