How severe is GHSA-6vqf-6fhm-7rc6?

GHSA-6vqf-6fhm-7rc6 has a CVSS score of 4.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-6vqf-6fhm-7rc6?

GHSA-6vqf-6fhm-7rc6 affects the following packages: openmage/magento-lts (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-6vqf-6fhm-7rc6?

Update openmage/magento-lts to 20.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6vqf-6fhm-7rc6 is resolved across your whole dependency graph.

How do I detect GHSA-6vqf-6fhm-7rc6 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openmage/magento-lts. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-6vqf-6fhm-7rc6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-6vqf-6fhm-7rc6?

O3 pinpoints whether GHSA-6vqf-6fhm-7rc6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-6vqf-6fhm-7rc6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6vqf-6fhm-7rc6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-6vqf-6fhm-7rc6?

GHSA-6vqf-6fhm-7rc6 is classified as Path Traversal (CWE-22), CWE-184 (CWE-184). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-6vqf-6fhm-7rc6 published, and has it been updated?

GHSA-6vqf-6fhm-7rc6 was published on April 21, 2026 and was last updated on April 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-6vqf-6fhm-7rc6

MEDIUM

GHSA-6vqf-6fhm-7rc6 is a medium-severity (CVSS 4.9) Path Traversal vulnerability in openmage/magento-lts. O3 Security confirms whether GHSA-6vqf-6fhm-7rc6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenMage LTS has a Path Traversal Filter Bypass in Dataflow Module

Also known asCVE-2026-25525

Published

Apr 21, 2026

Updated

Apr 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐘openmage/magento-lts

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

The Dataflow module in OpenMage LTS uses a weak blacklist filter (str_replace('../', '', $input)) to prevent path traversal attacks. This filter can be bypassed using patterns like ..././ or ....//, which after the replacement still result in ../. An authenticated administrator can exploit this to read arbitrary files from the server filesystem.

Metric	Value	Justification
Attack Vector (AV)	Network	Exploitable via admin panel
Attack Complexity (AC)	Low	Simple bypass pattern
Privileges Required (PR)	High	Requires admin authentication
User Interaction (UI)	None	No additional user interaction needed
Scope (S)	Unchanged	Impacts the vulnerable component
Confidentiality (C)	High	Can read sensitive system files
Integrity (I)	None	Read-only vulnerability
Availability (A)	None	No impact on availability

Affected Products

OpenMage LTS versions < 20.16.1
All versions derived from Magento 1.x with these code paths

Affected Files

File	Line	Vulnerable Code
`app/code/core/Mage/Dataflow/Model/Convert/Parser/Csv.php`	67	`str_replace('../', '', urldecode(...))`
`app/code/core/Mage/Dataflow/Model/Convert/Parser/Xml/Excel.php`	63	`str_replace('../', '', urldecode(...))`

Vulnerability Details

The Dataflow module allows administrators to import data from files. The files parameter specifies which file to import from the var/import/ directory. To prevent path traversal, the code uses str_replace() to remove ../ sequences:

$file = Mage::app()->getConfig()->getTempVarDir() . '/import/'
    . str_replace('../', '', urldecode(Mage::app()->getRequest()->getParam('files')));

However, str_replace() only performs a single pass, making it trivially bypassable:

Bypass Examples

Input	After `str_replace('../', '', ...)`	Result
`..././`	`../`	Bypass
`....//`	`../`	Bypass
`..././..././..././etc/passwd`	`../../../etc/passwd`	File read

Attack Scenario

Attacker gains admin access (via compromised credentials, social engineering, etc.)
Navigate to System > Import/Export > Dataflow Profiles
Create or modify an import profile
Set the files parameter to: ..././..././..././etc/passwd
Run the profile to read the contents of /etc/passwd

Proof of Concept

# Request to Dataflow with bypass pattern
GET /admin/system_convert_gui/run/id/1/?files=..././..././..././etc/passwd

# The str_replace removes '../' leaving:
# ..././..././..././etc/passwd -> ../../../etc/passwd

# Final path resolves to:
# /var/www/html/var/import/../../../etc/passwd -> /etc/passwd

Remediation

Replace the weak str_replace() filter with basename() to extract only the filename:

// Before (vulnerable)
$file = Mage::app()->getConfig()->getTempVarDir() . '/import/'
    . str_replace('../', '', urldecode(Mage::app()->getRequest()->getParam('files')));

// After (fixed)
$file = Mage::app()->getConfig()->getTempVarDir() . '/import/'
    . basename(urldecode(Mage::app()->getRequest()->getParam('files')));

Using basename() ensures only the filename portion is used, completely preventing any path traversal regardless of the input pattern.

Workarounds

If immediate upgrade is not possible:

Restrict admin access: Limit Dataflow access to trusted administrators only
Disable Dataflow: If not in use, disable the Dataflow module entirely
Web Application Firewall: Block requests containing path traversal patterns
File permissions: Ensure the web server user has minimal filesystem permissions
Monitor admin activity: Alert on suspicious Dataflow profile execution

Impact

An attacker with admin access can read sensitive files including:

/etc/passwd - System user information
app/etc/local.xml - Database credentials
.env files - Environment secrets
Log files - Potentially sensitive application data
Configuration files - Server and application configuration

Credit

This vulnerability was discovered and responsibly disclosed by blackhat2013 through HackerOne.

Timeline

2025-12-31: Vulnerability reported via HackerOne
2026-01-21: Fix developed and tested

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`openmage/magento-lts`	all versions	20.17.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openmage/magento-lts. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openmage/magento-lts to 20.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6vqf-6fhm-7rc6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-6vqf-6fhm-7rc6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6vqf-6fhm-7rc6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The Dataflow module in OpenMage LTS uses a weak blacklist filter (`str_replace('../', '', $input)`) to prevent path traversal attacks. This filter can be bypassed using patterns like `..././` or `....//`, which after the replacement still result in `../`. An authenticated administrator can exploit this to read arbitrary files from the server filesystem. | Metric | Value | Justification | | ------------------------ | --------- | ------------------------------------- | | Attack Vector (AV) | Network | Exploitable via admin panel |

O3 Security · Impact-Aware SCA

Is GHSA-6vqf-6fhm-7rc6 in your dependencies?

O3 detects GHSA-6vqf-6fhm-7rc6 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-6vqf-6fhm-7rc6

Blast Radius

Description

Affected Products

Affected Files

Vulnerability Details

Bypass Examples

Attack Scenario

Proof of Concept

Remediation

Workarounds

Impact

Credit

Timeline

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-6vqf-6fhm-7rc6 in your dependencies?