dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-13339

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

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
The Hippoo Mobile App for WooCommerce plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.7.1 via the template_redirect() function. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information.

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 · high confidence

The Hippoo Mobile App for WooCommerce WordPress plugin versions up to 1.7.1 contains a path traversal vulnerability in its template_redirect() function. This allows unauthenticated attackers to manipulate file path inputs using directory traversal sequences (e.g., ../../) to read sensitive files outside the intended web root directory.

MitigationUpdate to the latest version of Hippoo Mobile App for WooCommerce (beyond 1.7.1) which contains proper path validation. If immediate patching is not feasible, consider disabling the plugin or implementing web server-level access controls to restrict file read operations.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Confirm Hippoo plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'hippoo' or 'hippoo-mobile-app-for-woocommerce', or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if The Hippoo Mobile App for WooCommerce plugin appears in the list of installed plugins
  2. Identify installed plugin version
    Open the main plugin file (usually hippoo.php or index.php inside the plugin folder) and locate the 'Version' header in the plugin comment block, or check a dedicated version file if one exists
    Affected if The reported version is 1.7.1 or any version up to and including 1.7.1
  3. Verify the template_redirect function exists
    Locate the plugin source files and search for the function 'template_redirect' - this is a WordPress hook that fires before determining which template to load
    Affected if The template_redirect function is present in the plugin code, indicating the vulnerable code path exists
  4. Inspect the file path handling in template_redirect
    Examine the template_redirect function code for any file operation (such as file_get_contents, fopen, include, require) that uses user-controlled input without proper sanitization (look for lack of realpath(), basename(), or path validation)
    Affected if The function contains file read operations using unsanitized input parameters that accept directory traversal sequences like ../
  5. Review access logs for exploitation attempts
    Search web server access logs (Apache, Nginx, or WAF logs) for requests to this WordPress site containing patterns like '../', '..\', or absolute path references that may indicate path traversal probing
    Affected if Log entries show directory traversal patterns targeting the Hippoo plugin endpoint, suggesting active exploitation

A user is affected if the Hippoo Mobile App for WooCommerce plugin is installed with version 1.7.1 or lower AND the template_redirect function contains vulnerable file path handling without proper sanitization.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of Hippoo Mobile App for WooCommerce (beyond 1.7.1) which contains proper path validation. If immediate patching is not feasible, consider disabling the plugin or implementing web server-level access controls to restrict file read operations.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13339 — 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-13339 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