OroPlatform vulnerable to path traversal during temporary file manipulations
CVE-2022-41951GHSA-9v3j-4j64-p937
What to do
Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist oro/platform
- Affected
- >= 4.1.0, <= 4.1.13>= 4.2.0, <= 4.2.10>= 5.0.0, < 5.0.8
- Fixed in
- 5.0.8
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-9v3j-4j64-p937 lists affected ranges: Packagist oro/platform >=4.1.0 =4.2.0 =5.0.0 <5.0.8
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.5 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
- EPSS
- CVE-2022-41951: 0.95% estimated exploitation activity in the next 30 days; percentile 61.18 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact Path Traversal is possible in Oro\Bundle\GaufretteBundle\FileManager::getTemporaryFileName. With this method, an attacker can pass the path to a non-existent file, which will allow writing the content to a new file that will be available during script execution. The file will be deleted immediately after the script ends. Workarounds Apply patch Or decorate Oro\Bundle\GaufretteBundle\FileManager::getTemporaryFileName in your customization and clear $suggestedFileName argument References - Path Traversal - How to Decorate Services
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-9v3j-4j64-p937
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2022-41951 Advisory: OroPlatform vulnerable to path traversal during temporary file manipulations IDs: CVE-2022-41951, GHSA-9v3j-4j64-p937 Record: https://patchnext.com/advisories/cve-2022-41951 (revision 1, source checked 26 Oct 2026, 14:11 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Partial vendor fix; fixed versions by package: oro/platform 5.0.8. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist oro/platform: affected >= 4.1.0, <= 4.1.13; >= 4.2.0, <= 4.2.10; >= 5.0.0, < 5.0.8; fixed in 5.0.8 ## Suggested inspection (read-only) - Packagist oro/platform: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on oro/platform. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-9v3j-4j64-p937 (GitHub-reviewed advisory GHSA-9v3j-4j64-p937 lists affected ranges: Packagist oro/platform >=4.1.0 =4.2.0 =5.0.0 <5.0.8) Commands are suggestions: review each one before running it.
Loading voting…