CVE-2025-58949

8.1 HIGH

📋 TL;DR

This vulnerability allows attackers to include local PHP files through improper filename control in the Spock WordPress theme. It enables PHP Local File Inclusion (LFI) which can lead to sensitive information disclosure or code execution. All WordPress sites using Spock theme version 1.17 or earlier are affected.

💻 Affected Systems

Products:
  • axiomthemes Spock WordPress theme
Versions: n/a through <= 1.17
Operating Systems: Any OS running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with Spock theme active. PHP configuration with allow_url_include disabled does not prevent this LFI.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full server compromise through LFI to Remote Code Execution (RCE) chain, potentially allowing complete control of the web server and underlying system.

🟠

Likely Case

Sensitive file disclosure including configuration files, database credentials, and user data, potentially leading to further attacks.

🟢

If Mitigated

Limited impact with proper file permissions and web server hardening, potentially only allowing read access to non-sensitive files.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Simple path traversal techniques can exploit this vulnerability. Public exploit code is available in security advisories.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: >1.17

Vendor Advisory: https://patchstack.com/database/Wordpress/Theme/spock/vulnerability/wordpress-spock-theme-1-17-local-file-inclusion-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Appearance > Themes. 3. Check if Spock theme update is available. 4. Update to latest version (>1.17). 5. Clear cache if using caching plugins.

🔧 Temporary Workarounds

Disable vulnerable theme

all

Temporarily switch to default WordPress theme until patch is applied

wp theme activate twentytwentyfour

Restrict file access

linux

Implement web server restrictions to prevent directory traversal

# Apache: Add to .htaccess
<FilesMatch "\.(php|inc)$">
Order Deny,Allow
Deny from all
</FilesMatch>
# Nginx: Add to server block
location ~ \.php$ {
    try_files $uri =404;
    fastcgi_param PHP_ADMIN_VALUE "open_basedir=/var/www/html";
}

🧯 If You Can't Patch

  • Implement Web Application Firewall (WAF) rules to block LFI patterns and path traversal attempts
  • Apply strict file permissions and disable PHP execution in upload directories

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Appearance > Themes for Spock theme version. If version is 1.17 or lower, system is vulnerable.

Check Version:

wp theme list --name=spock --field=version

Verify Fix Applied:

Verify Spock theme version is >1.17 in WordPress admin panel and test LFI payloads return 404/403 errors instead of file contents.

📡 Detection & Monitoring

Log Indicators:

  • HTTP requests containing '../' patterns targeting PHP files
  • Unusual file access patterns in web server logs
  • Failed attempts to access sensitive system files

Network Indicators:

  • HTTP requests with path traversal sequences in parameters
  • Unusual file extensions in URL parameters

SIEM Query:

source="web_access.log" AND (url="*../*" OR url="*..%2f*" OR url="*..%5c*") AND (url="*.php*" OR url="*.inc*")

🔗 References

📤 Share & Export