EUVD-2025-17511
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
3Tags
Description
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in WebGeniusLab Seofy Core allows PHP Local File Inclusion. This issue affects Seofy Core: from n/a through 1.4.5.
Analysis
Path traversal vulnerability in WebGeniusLab Seofy Core (versions up to 1.4.5) that allows unauthenticated remote attackers to achieve PHP Local File Inclusion (LFI) with high complexity. The vulnerability enables attackers to read arbitrary files and potentially execute code on affected systems. No public indicators confirm active exploitation or KEV listing at this time, but the high CVSS score (8.1) and remote attack vector indicate significant risk requiring urgent patching.
Technical Context
This is a CWE-22 (Improper Limitation of Pathname to Restricted Directory) vulnerability, a classic path traversal flaw where user-supplied input is not properly sanitized before being used in file path operations. In Seofy Core (a WordPress/PHP-based SEO plugin), the vulnerability likely exists in file inclusion operations where an attacker can manipulate path parameters (e.g., using '../' sequences or null bytes) to escape intended directories and access sensitive system files (/etc/passwd, wp-config.php, etc.) or include arbitrary PHP files. The medium-high attack complexity (AC:H) suggests some conditions must be met (e.g., specific server configuration, bypass of basic filtering), but the network attack vector (AV:N) and lack of authentication requirement (PR:N) make this remotely exploitable at scale. Affected CPE likely includes: cpe:2.3:a:webgeniuslab:seofy_core:*:*:*:*:*:*:*:* (versions <=1.4.5).
Affected Products
WebGeniusLab Seofy Core (1.4.5 and all prior versions)
Remediation
Upgrade Seofy Core to version 1.4.6 or later (assumed patch version; verify with vendor); priority: Immediate; source: WebGeniusLab official plugin repository / vendor advisory Workaround (Temporary): Disable Seofy Core plugin until patch is available; use alternative SEO plugin with verified security record; priority: High Mitigation (Defense-in-Depth): ['Apply Web Application Firewall (WAF) rules to block path traversal patterns (../, ..\\, %2e%2e/, null bytes) in HTTP requests', 'Implement strict file upload/inclusion policies at the PHP level (disable allow_url_include, use open_basedir)', 'Monitor for suspicious file access patterns in web server logs', 'Restrict file permissions on sensitive directories (wp-config.php, wp-admin, etc.)', 'Keep WordPress core and all plugins updated']; priority: Medium-High Detection: Check web logs for requests containing ../, ..\, %2e%2e, or encoded variants targeting Seofy Core endpoints; look for 200/302 responses that may indicate successful file inclusion
Priority Score
Share
External POC / Exploit Code
Leaving vuln.today