CVE-2025-27362

8.1 HIGH

📋 TL;DR

This vulnerability allows attackers to include local files on the server through improper filename control in PHP include/require statements. It affects WordPress sites using the BZOTheme Petito theme, potentially leading to sensitive information disclosure or code execution. All installations using Petito theme versions up to 1.6.2 are vulnerable.

💻 Affected Systems

Products:
  • BZOTheme Petito WordPress Theme
Versions: n/a through 1.6.2
Operating Systems: All operating systems running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with Petito theme active. PHP configuration with allow_url_include disabled does not prevent this local file inclusion vulnerability.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full server compromise through local file inclusion leading to remote code execution, sensitive file disclosure (including configuration files with database credentials), and complete site takeover.

🟠

Likely Case

Sensitive information disclosure through reading configuration files (wp-config.php), log files, or other sensitive system files, potentially leading to database access or further exploitation.

🟢

If Mitigated

Limited impact with proper file permissions and security controls, potentially only allowing reading of non-sensitive files or triggering PHP errors.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires no authentication and uses simple HTTP requests with path traversal or file inclusion parameters. Public proof-of-concept code is available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.6.3 or later

Vendor Advisory: https://patchstack.com/database/wordpress/theme/bw-petito/vulnerability/wordpress-petito-1-6-2-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 Petito theme update is available. 4. Update to version 1.6.3 or later. 5. Alternatively, download updated theme from vendor and manually replace files.

🔧 Temporary Workarounds

Disable vulnerable theme

all

Temporarily switch to default WordPress theme to remove vulnerability

wp theme activate twentytwentyfour

Web application firewall rule

linux

Block requests containing path traversal sequences in theme parameters

# Example mod_security rule: SecRule ARGS "\.\./" "id:1001,phase:2,deny,status:403,msg:'Path traversal attempt'

🧯 If You Can't Patch

  • Remove or disable the Petito theme completely and use a different theme
  • Implement strict file permissions (chmod 644 for PHP files, 755 for directories) and disable directory listing

🔍 How to Verify

Check if Vulnerable:

Check WordPress theme version in wp-content/themes/petito/style.css or via WordPress admin panel > Appearance > Themes

Check Version:

grep 'Version' wp-content/themes/petito/style.css | head -1

Verify Fix Applied:

Verify theme version is 1.6.3 or higher and test file inclusion attempts return errors instead of file contents

📡 Detection & Monitoring

Log Indicators:

  • HTTP requests with ../ sequences in theme-related parameters
  • PHP warnings about file inclusion failures
  • Access to sensitive files like wp-config.php from web requests

Network Indicators:

  • HTTP GET requests with file inclusion parameters (e.g., ?file=../../../wp-config.php)
  • Unusual file access patterns to non-theme directories

SIEM Query:

source="web_access_logs" AND (uri="*../*" OR uri="*wp-config.php*") AND user_agent NOT IN ("bot", "scanner")

🔗 References

📤 Share & Export