CVE-2025-58934

8.1 HIGH

📋 TL;DR

This vulnerability allows attackers to include local files on the server through PHP's include/require statements in the The Gig WordPress theme. Attackers can potentially read sensitive files or execute arbitrary code. All WordPress sites using The Gig theme version 1.18.0 or earlier are affected.

💻 Affected Systems

Products:
  • axiomthemes The Gig WordPress theme
Versions: n/a through <= 1.18.0
Operating Systems: All operating systems running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with The Gig theme active. PHP configuration with allow_url_include disabled does not prevent local file inclusion.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete server compromise, data theft, and website defacement.

🟠

Likely Case

Sensitive file disclosure including configuration files, database credentials, and user data.

🟢

If Mitigated

Limited impact if file permissions are restrictive and web server runs with minimal privileges.

🌐 Internet-Facing: HIGH - WordPress themes are typically internet-facing and accessible to unauthenticated users.
🏢 Internal Only: MEDIUM - Internal WordPress installations could still be targeted by authenticated users or through other attack vectors.

🎯 Exploit Status

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

Local File Inclusion vulnerabilities are commonly exploited and require minimal technical skill. The vulnerability is documented on security databases.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: >1.18.0

Vendor Advisory: https://patchstack.com/database/Wordpress/Theme/thegig/vulnerability/wordpress-the-gig-theme-1-18-0-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 The Gig theme has an update available. 4. Update to latest version. 5. If no update available, replace with patched version from official source.

🔧 Temporary Workarounds

Disable vulnerable theme

all

Switch to a different WordPress theme until patch is available

wp theme activate twentytwentyfour
wp theme deactivate thegig

Restrict file access

linux

Configure web server to deny access to sensitive directories

# In .htaccess for Apache:
<FilesMatch "\.(php|inc|conf|config)$">
  Deny from all
</FilesMatch>
# In nginx config:
location ~ /\.(php|inc|conf|config)$ {
  deny all;
}

🧯 If You Can't Patch

  • Implement Web Application Firewall (WAF) rules to block LFI patterns
  • Restrict PHP execution in upload directories and disable dangerous PHP functions

🔍 How to Verify

Check if Vulnerable:

Check WordPress theme version in Appearance > Themes or run: wp theme list --field=name,version | grep thegig

Check Version:

wp theme list --field=name,version | grep thegig

Verify Fix Applied:

Confirm theme version is >1.18.0 and test LFI payloads return errors instead of file contents

📡 Detection & Monitoring

Log Indicators:

  • Unusual include/require statements in PHP error logs
  • Requests with ../ patterns or file path traversal attempts
  • Access to sensitive files like /etc/passwd, wp-config.php

Network Indicators:

  • HTTP requests with file path parameters containing traversal sequences
  • Unexpected file downloads from web server

SIEM Query:

source="web_server_logs" AND (uri="*../*" OR uri="*..%2f*" OR uri="*..%5c*") AND (uri="*.php*" OR uri="*.inc*" OR uri="*wp-config*" OR uri="*etc/passwd*")

🔗 References

📤 Share & Export