Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Possibility for Denial of Service by overwriting PHP files with language exports

GHSA-3fvf-2gp4-89wq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (barryvdh/laravel-translation-manager 0.6.2), redeploy, then verify what is actually installed.

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.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Impact Laravel Translation Manager didn't check the locale name, which allowed directory traversal when exporting files. The content would be a PHP file returning an array of translations, but this could lead to unexpected results, like denial of service. Access to the Laravel Translation Manager is required, because a new locale would have to be added and published. Patches Version 0.6.2 fixes this issue. Workarounds Only allow trusted admins to publish/edit translations. References https://github.com/barryvdh/laravel-translation-manager/pull/417 For more information If you have any questions or comments about this advisory: Open an issue in https://github.com/barryvdh/laravel-translation-manager Email me (see Github profile) Credits Found and reported by Natalia Trojanowska

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-3fvf-2gp4-89wq

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-3fvf-2gp4-89wq

Advisory: Possibility for Denial of Service by overwriting PHP files with language exports
IDs: GHSA-3fvf-2gp4-89wq
Record: https://patchnext.com/advisories/ghsa-3fvf-2gp4-89wq (revision 1, source checked 26 Oct 2026, 13:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: barryvdh/laravel-translation-manager 0.6.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist barryvdh/laravel-translation-manager: affected < 0.6.2; fixed in 0.6.2

## Suggested inspection (read-only)
- Packagist barryvdh/laravel-translation-manager: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on barryvdh/laravel-translation-manager.
- 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-3fvf-2gp4-89wq (GitHub-reviewed advisory GHSA-3fvf-2gp4-89wq lists affected ranges: Packagist barryvdh/laravel-translation-manager >=0 <0.6.2)

Commands are suggestions: review each one before running it.

Loading voting…