CVE Alert: CVE-2025-10897 – JMA Plugins – WooCommerce Designer Pro

CVE-2025-10897

HIGHNo exploitation known

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.

CVSS v3.1 (8.6)
Vendor
JMA Plugins
Product
WooCommerce Designer Pro
Versions
* lte 1.9.28
CWE
CWE-22, CWE-22 Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Published
2025-10-31T07:26:39.837Z
Updated
2025-10-31T07:26:39.837Z

AI Summary Analysis

Risk verdict

High risk: unauthenticated remote arbitrary file read could disclose sensitive config data; exploit is feasible without user interaction, warranting urgent action.

Why this matters

Reading restricted server files can reveal database credentials and other secrets, enabling direct DB access or further compromise. The impact includes data confidentiality loss, possible site defacement, and downstream customer trust/ compliance concerns.

Most likely attack path

An attacker remotely targets an exposed installation, exploiting a path traversal flaw to read restricted files. No user interaction or privileges are required; if wp-config.php or similar secrets are retrieved, the attacker can attempt direct database access and pivot to adjacent components.

Who is most exposed

Public-facing WordPress sites with the affected plugin installed, especially those on shared hosting or under-resourced security controls, are most at risk. Environments with weak file permissions or poor secret management amplify exposure.

Detection ideas

  • Look for suspicious GET requests containing path traversal patterns (e.g., ../../) targeting wp-config.php or other config files.
  • Unusual spikes in 404/403 responses from diverse IPs targeting plugin endpoints.
  • Unexpected reads of application configuration or credential-like strings in web logs or memory dumps.
  • WAF or reverse proxy blocks consistent with traversal attempts.
  • Anomalous database connection attempts following unusual file-access events.

Mitigation and prioritisation

  • Apply the latest patch or upgrade to a non-vulnerable version; if unavailable, disable or remove the plugin until fixed.
  • Enforce strict file permissions and restrict access to configuration files; review secret storage practices.
  • Implement a web application firewall rule to block directory traversal attempts against sensitive paths.
  • Verify backups and rehearse recovery; monitor for signs of credential exposure and database access activity.
  • Change management: prioritise remediation promptly; escalate if KEV/EPSS indicators appear in your risk signals.

Support Our Work

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.

AI APIs OSINT driven New features