CVE-2025-68002

Open User Map <= 1.4.16 - Authenticated (Subscriber+) Arbitrary File Download

2026-02-16 00:00
Phat RiO

Strategic Overview

Status
Patched in 1.4.17
Affected Plugin
Open User Map – Interactive Leaflet Maps
Affected Version
<= 1.4.16
CVSS
6.5Medium
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2025-68002
View all Open User Map – Interactive Leaflet Maps vulnerabilities

At a glance

CVE-2025-68002 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Open User Map WordPress plugin, affecting versions <= 1.4.16. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.4.17; sites on affected versions should update now. Disclosed February 2026, reported by Phat RiO.

Vulnerability Overview

The Open User Map plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.4.16. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.

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. A successful exploit has high impact on confidentiality.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in Open User Map <= 1.4.16 takes an account at Subscriber 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 Open User Map the fix is 1.4.17: builds <= 1.4.16 are affected, anything from 1.4.17 onward is not.

Remediation

Update to version 1.4.17, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber 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: Open User Map 1.4.17 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-68002https://www.wordfence.com/threat-intel/vulnerabilities/id/baff5795-f164-489e-8f57-536174867ec5https://nvd.nist.gov/vuln/detail/CVE-2025-68002

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C