GPX Viewer <= 2.2.11 - Authenticated (Editor+) Path Traversal
Strategic Overview
- Status
- Patched in 2.2.12
- Affected Plugin
- GPX Viewer
- Affected Version
<= 2.2.11- CVSS
- 2.7Low
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2025-27274
At a glance
CVE-2025-27274 is a low-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the GPX Viewer WordPress plugin, affecting versions <= 2.2.11. It carries a CVSS score of 2.7 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 2.2.12; sites on affected versions should update now. Disclosed February 2025, reported by Trương Hữu Phúc (truonghuuphuc).
Vulnerability Overview
The GPX Viewer plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 2.2.11. This makes it possible for authenticated attackers, with Editor-level access and above, to perform actions on files outside of the originally intended directory.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in GPX Viewer <= 2.2.11 takes an account at Editor level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For GPX Viewer the fix is 2.2.12: builds <= 2.2.11 are affected, anything from 2.2.12 onward is not.
Remediation
Update to version 2.2.12, or a newer patched version
How does WordSec protect against this?
An attacker needs Editor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: GPX Viewer 2.2.12 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in GPX Viewer
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C