CVE-2025-10897
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 · uneditedThe 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.
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 confidenceThe WooCommerce Designer Pro theme for WordPress contains an arbitrary file read vulnerability in all versions up to 1.9.28, allowing unauthenticated attackers to access any file on the server filesystem. This critical flaw enables exposure of sensitive configuration files, most notably wp-config.php which contains database credentials.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WooCommerce Designer Pro theme is installedCheck your WordPress installation's wp-content/themes/ directory for a folder named 'designer-pro' or 'woocommercedesignerpro'. You can also list installed themes via WP-CLI: wp theme list --status=activeAffected if The theme folder exists in your WordPress themes directory
-
Confirm the installed theme versionOpen the theme's style.css file in the theme folder and look for the 'Version:' header in the file comments. Alternatively, check via WP-CLI: wp theme get designer-proAffected if The version listed is 1.9.28 or lower
-
Identify the vulnerable file read endpointSearch the theme folder for PHP files that contain file reading functions like file_get_contents, fopen, readfile, or include/require with user-controlled input. Look for parameters like 'file', 'path', 'src', or 'file_path' in the code. Common vulnerable patterns: $_GET['file'], request::get('file')Affected if A PHP file in the theme accepts a file path parameter and reads files from the filesystem without proper validation
-
Test if arbitrary file access is possibleUsing a web proxy or curl, send a request to the suspected vulnerable endpoint with a parameter like ?file=../../wp-config.php or ?file=/etc/passwd to see if the file contents are returned. Start with a benign test: ?file=../../../../wp-config.phpAffected if The server returns the contents of wp-config.php or other sensitive system files in the response
Your environment is affected if the WooCommerce Designer Pro theme is installed with version 1.9.28 or lower AND the vulnerable file read endpoint is accessible and returns file contents.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the WooCommerce Designer Pro theme to a version newer than 1.9.28 as soon as a patch is released. If no patch is available, consider removing the theme entirely or implement web application firewall rules to block requests to the vulnerable endpoint.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10897 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10897 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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