{"items":[{"id":"NVI-00004621","kind":"vulnerability","title":"Symfony SSRF Vulnerability via Form Component","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-cqqh-94r6-wjrg","CVE-2017-16790"],"plain_summary":"OSV carries this publisher advisory for symfony/form, symfony/form, symfony/form, symfony/form, symfony/symfony. 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.7.38 for symfony/form. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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.8.31 for symfony/form. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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 3.2.14 for symfony/form. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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 3.3.13 for symfony/form. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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.7.38 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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.8.31 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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 3.2.14 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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 3.3.13 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-990ce2e4a82e0fcb4d09c5882dab2ce9"],"action_type":"investigate","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":[{"kind":"CVSS","as_of":"2026-06-17T01:09:55.853Z","value":"4 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-16d86d4acafdc98e1f4f5652cfcca309"},{"kind":"CVSS","as_of":"2026-06-17T01:09:55.853Z","value":"6.5 MEDIUM (3.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-16d86d4acafdc98e1f4f5652cfcca309"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"1.568%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.75338. Missing scores are unknown.","source_id":"sr-990ce2e4a82e0fcb4d09c5882dab2ce9"}],"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-6d2fdb6fb8914adb329813dd1d83a8af","url":"https://github.com/advisories/GHSA-cqqh-94r6-wjrg","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-cqqh-94r6-wjrg","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.702Z"},{"id":"sr-16d86d4acafdc98e1f4f5652cfcca309","url":"https://nvd.nist.gov/vuln/detail/CVE-2017-16790","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2017-16790","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T21:56:48.322Z"},{"id":"sr-990ce2e4a82e0fcb4d09c5882dab2ce9","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2017-16790","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/form","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 2.7.0; fixed 2.7.38"]},{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/form","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.8.31"]},{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/form","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.2.14"]},{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/form","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.13"]},{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 2.7.0; fixed 2.7.38"]},{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.8.31"]},{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.2.14"]},{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.13"]}],"null_published_at":"2026-11-04T02:53:03.157Z","source_updated_at":"2024-04-25T22:28:47.780Z","source_disclosed_at":"2022-05-14T02:41:31.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:10.702Z"},{"id":"NVI-00004621","kind":"vulnerability","title":"Symfony SSRF Vulnerability via Form Component","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-cqqh-94r6-wjrg","CVE-2017-16790"],"plain_summary":"OSV carries this publisher advisory for symfony/form, symfony/form, symfony/form, symfony/form, symfony/symfony. 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.7.38 for symfony/form. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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.8.31 for symfony/form. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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 3.2.14 for symfony/form. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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 3.3.13 for symfony/form. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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.7.38 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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.8.31 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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 3.2.14 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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 3.3.13 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"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":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-16d86d4acafdc98e1f4f5652cfcca309"],"action_type":"investigate","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":[{"kind":"CVSS","as_of":"2026-06-17T01:09:55.853Z","value":"4 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-16d86d4acafdc98e1f4f5652cfcca309"},{"kind":"CVSS","as_of":"2026-06-17T01:09:55.853Z","value":"6.5 MEDIUM (3.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-16d86d4acafdc98e1f4f5652cfcca309"}],"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-6d2fdb6fb8914adb329813dd1d83a8af","url":"https://github.com/advisories/GHSA-cqqh-94r6-wjrg","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-cqqh-94r6-wjrg","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.702Z"},{"id":"sr-16d86d4acafdc98e1f4f5652cfcca309","url":"https://nvd.nist.gov/vuln/detail/CVE-2017-16790","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2017-16790","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T21:56:48.322Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/form","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 2.7.0; fixed 2.7.38"]},{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/form","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.8.31"]},{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/form","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.2.14"]},{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/form","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.13"]},{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 2.7.0; fixed 2.7.38"]},{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.8.31"]},{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.2.14"]},{"certainty":"source_listed","source_ids":["sr-6d2fdb6fb8914adb329813dd1d83a8af"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a \"FileType\" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, \"file:///etc/passwd\"). If the application did not perform any additional checks about the value submitted to the \"FileType\", the contents of the given file on the server could have been exposed to the attacker.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.13"]}],"null_published_at":"2026-10-31T22:13:35.640Z","source_updated_at":"2024-04-25T22:28:47.780Z","source_disclosed_at":"2022-05-14T02:41:31.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:10.702Z"}],"next_cursor":null,"snapshot_revision":"40769"}