CVE-2025-47535
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in wpopal Opal Woo Custom Product Variation opal-woo-custom-product-variation allows Path Traversal.This issue affects Opal Woo Custom Product Variation: from n/a through <= 1.2.0.
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 confidenceA path traversal vulnerability in the Opal Woo Custom Product Variation WordPress plugin (versions up to 1.2.0) allows attackers to access files outside the intended directory by manipulating file paths with '..' sequences. This could enable unauthorized reading of sensitive server files.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installationNavigate to WordPress admin > Plugins > Installed Plugins and search for 'Opal Woo Custom Product Variation', or inspect the /wp-content/plugins/ directory for a folder named similar to 'opal-woo-custom-product-variation'Affected if The plugin is installed and active in WordPress
-
Identify installed versionIn WordPress admin, click on the plugin to view details and note the version number displayed, or check the plugin's main PHP file for a 'Version:' comment in the file headerAffected if Version cannot be determined or is older than the patched release (no specific version range provided in CVE)
-
Check for exposed file operation endpointsReview the plugin directory for PHP files handling file operations (look for functions like file_get_contents, readfile, fopen, include, require), or use a vulnerability scanner to probe the plugin's AJAX and REST API endpointsAffected if The plugin exposes any file read or include functionality accessible via HTTP request parameters
-
Inspect web server access logsSearch access logs (usually in /var/log/apache2/access.log or similar) for requests to the plugin containing path traversal sequences like '..', '../', or absolute paths such as '/etc/passwd'Affected if Log entries show suspicious requests with '../' or absolute file paths targeting plugin endpoints
-
Verify input sanitizationExamine the plugin's PHP source code for file path parameters and check if they use basename(), realpath(), or similar sanitization functions before performing file operationsAffected if File operations lack proper path sanitization using basename/realpath checks
The environment is likely affected if the Opal Woo Custom Product Variation plugin is installed and exposes file operation functionality without proper path traversal protection.
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 to the latest version of Opal Woo Custom Product Variation; if no patch exists, disable the plugin until a fix is available, or implement input validation to sanitize file path parameters and restrict access to allowed directories.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47535 — 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-47535 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