dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-23422

HIGH · 7.5 CVSS v3.1 Published 2025-01-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in moaluko Store Locator store-locator allows PHP Local File Inclusion.This issue affects Store Locator: from n/a through <= 3.98.10.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A path traversal vulnerability in the moaluko Store Locator WordPress plugin (versions <= 3.98.10) allows attackers to use directory traversal sequences (e.g., ../../) to access files outside the intended web root directory. The vulnerability is a PHP Local File Inclusion (LFI) issue, potentially enabling unauthorized reading of sensitive files or, in certain configurations, remote code execution.

MitigationUpdate the Store Locator plugin to the latest patched version once released. Until then, implement input validation to reject path traversal sequences (../) in user-supplied parameters, or deploy a WAF rule to block such requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Store Locator plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'moaluko Store Locator' or 'Store Locator' by moaluko. Alternatively, check the /wp-content/plugins/ directory for a folder named 'moaluko-store-locator' or similar.
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin plugin list, check the version column for the Store Locator plugin. Or inspect the main plugin PHP file (e.g., store-locator.php) in the plugin directory and look for the 'Version:' header comment.
    Affected if Version is 3.98.10 or lower, or if the version cannot be determined (indicating an older unlisted release)
  3. Identify the vulnerable file inclusion endpoint
    Review plugin source code for PHP files that use include, require, include_once, or require_once with user-supplied parameters. Look for parameters that might accept file paths (commonly named 'file', 'path', 'template', 'page', 'slug', or similar).
    Affected if A PHP file exists that dynamically includes files based on request parameters without proper sanitization
  4. Confirm the path traversal vulnerability is present
    If a file inclusion endpoint is found, test it with a path traversal sequence such as ../../../../wp-config.php in the suspected parameter. Check if the server returns file contents or an error revealing successful traversal.
    Affected if The parameter accepts directory traversal sequences and returns or processes file contents outside the intended directory
  5. Check for sensitive file exposure
    If traversal is confirmed, verify access to sensitive files like wp-config.php, .htaccess, or other configuration files in parent directories.
    Affected if The plugin allows reading of files outside the plugin's directory through path traversal

The environment is affected if the moaluko Store Locator plugin version is 3.98.10 or lower AND the plugin contains a file inclusion mechanism that accepts unsanitized user input, allowing ../ sequences to access files outside the intended directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Store Locator plugin to the latest patched version once released. Until then, implement input validation to reject path traversal sequences (../) in user-supplied parameters, or deploy a WAF rule to block such requests.

Recommended fix Moderate confidence

Latest available version of moaluko Store Locator plugin (version > 3.98.10)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Store Locator' (moaluko Store Locator) plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. After updating, verify the plugin is functioning correctly on the frontend
  6. 6. If automatic updates are not enabled, manually download the latest version from the WordPress Plugin Directory and reinstall

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23422 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-23422 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data