CVE-2025-28955
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 FWDesign Easy Video Player Wordpress & WooCommerce fwdevp allows Path Traversal.This issue affects Easy Video Player Wordpress & WooCommerce: from n/a through <= 10.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 FWDesign Easy Video Player WordPress/WooCommerce plugin (fwdevp) allows attackers to access files outside the intended directory by manipulating file paths with traversal sequences (e.g., ../../). This occurs due to insufficient input validation on file path parameters, potentially exposing sensitive system 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installation statusIn WordPress admin, go to Plugins > Installed Plugins and look for 'FWDesign Easy Video Player' or 'fwdevp'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'fwdevp' or similar.Affected if The plugin is installed and active on the WordPress site
-
Identify the installed plugin versionIn WordPress admin, click on the plugin to view its details and note the version number. Alternatively, check the plugin's main PHP file header for the Version field.Affected if The installed version is unknown or within an unpatched version range
-
Locate file handling code pathsSearch the plugin directory for code that processes file path parameters, typically in PHP files that handle video file requests or include/require statements using user-supplied paths. Look for patterns like $_GET, $_POST, or $_REQUEST handling file paths.Affected if The plugin contains code that accepts file path parameters without proper sanitization
-
Inspect for vulnerable file inclusion functionsExamine the identified file handling code for direct use of user input in include, require, include_once, require_once, file_get_contents, or similar functions without realpath() validation or directory boundary checks.Affected if File path parameters are used directly in inclusion or reading functions without traversal protection
-
Test for path traversal vulnerabilityIf accessible, send a request with a crafted path parameter containing traversal sequences (e.g., ../../../../etc/passwd) to the suspected endpoint. Compare the response against a request for a known valid file within the intended directory.Affected if The application returns contents of files outside the intended video directory when traversal sequences are used
The environment is affected if the FWDesign Easy Video Player plugin is installed, processes file path parameters, and lacks proper path sanitization using realpath() or equivalent boundary checks.
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 dataImplement strict input validation and path sanitization using functions like realpath() to ensure requested files remain within allowed directories. Update to a patched version if available from the vendor.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28955 — 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-28955 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