CVE-2025-39473
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 WebGeniusLab Seofy Core seofy-core allows PHP Local File Inclusion.This issue affects Seofy Core: from n/a through <= 1.6.8.
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 Seofy Core plugin version 1.6.8 and below allows unauthenticated attackers to manipulate file path parameters to include arbitrary PHP files from restricted directories, enabling local file inclusion (LFI) attacks.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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.
-
Verify Seofy Core plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'seofy-core' or similar. If using WordPress admin, navigate to Plugins > Installed Plugins and look for 'Seofy Core'.Affected if The plugin is not found in the WordPress installation.
-
Identify the installed version of Seofy CoreLocate the main plugin PHP file (usually seofy-core.php or similar in the plugin folder) and read the 'Version' header comment at the top of the file. Alternatively, check in WordPress admin under Plugins > Installed Plugins where the version number is displayed.Affected if The version number is 1.6.8 or lower.
-
Locate the vulnerable file inclusion codeSearch plugin PHP files for functions that include or require files based on user input, such as 'include()', 'require()', 'include_once()', or 'require_once()' combined with parameters like 'file', 'path', 'template', 'slug', or 'page'. Look for lack of sanitization using functions like 'realpath()' or 'basename()'.Affected if File inclusion functions accepting unsanitized user-controlled path parameters are found.
-
Identify accessible endpoints using the vulnerable parameterExamine the plugin's router or initialization files to determine which URL parameters trigger the file inclusion. Test suspected parameters (e.g., ?file= or ?path=) on the frontend to confirm they are accessible without authentication.Affected if The file inclusion parameter is reachable via HTTP request without login and accepts path traversal sequences like '../'.
A user is affected if the Seofy Core plugin version is 1.6.8 or lower AND the plugin exposes an unauthenticated file inclusion mechanism that accepts path traversal input.
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 dataUpgrade to a patched version of Seofy Core. If no patch is available, implement strict input validation on file path parameters using whitelisting, enforce directory containment checks (e.g., realpath()), and disable PHP file inclusion from user-controlled paths.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39473 — 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-39473 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