Path Traversal in WooCommerce Designer Pro (WordPress theme) (CVE-2025-10897)
Summary
Path traversal in WooCommerce Designer Pro (WordPress theme) (CVE-2025-10897). Confidential information can be exposed externally.
Original description
The description as published by the source.
The WooCommerce Designer Pro theme for WordPress is vulnerable to arbitrary file read in all versions up to, and including, 1.9.28. This makes it possible for unauthenticated attackers to read arbitrary files on the server, which can expose DB credentials when the wp-config.php file is read.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-10897 has been found in WooCommerce Designer Pro (WordPress theme).
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WooCommerce Designer Pro (WordPress theme) CVE-2025-10897" on the vendor's site.
CVE-2025-10897 (WooCommerce Designer Pro (WordPress theme)) — CWE-22 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in WooCommerce Designer Pro (WordPress theme).
Check the vendor advisory for the affected versions of WooCommerce Designer Pro (WordPress theme).
Severity: High (CVSS 8.6/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで WooCommerce Designer Pro (WordPress theme) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。