CVE-2025-60058
WordPress vulnerability analysis and mitigation

Overview

CVE-2025-60058 is a PHP Local File Inclusion (LFI) vulnerability in the AncoraThemes DetailX WordPress theme, affecting all versions up to and including 1.10.0. The flaw stems from improper control of filename parameters used in PHP include/require statements (CWE-98). It was reported by security researcher "Bonds" on July 20, 2025, and published by Patchstack on August 19, 2025. The vulnerability carries a CVSS v3.1 base score of 8.1 (High), exploitable by unauthenticated remote attackers (Patchstack).

Technical details

The vulnerability is classified under CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program). The DetailX theme fails to properly sanitize or validate user-supplied input before using it in PHP file inclusion functions, allowing an attacker to manipulate the filename parameter to reference arbitrary local files on the server. Exploitation requires no authentication and no user interaction, though attack complexity is rated High, suggesting some precondition or bypass is needed. The vulnerability maps to CAPEC-193 (PHP Remote File Inclusion) and OWASP Top 10 category A3: Injection (Patchstack).

Impact

Successful exploitation allows an unauthenticated attacker to read arbitrary local files on the web server, including sensitive configuration files such as wp-config.php, which contains database credentials. This could lead to complete database takeover, exposure of secret keys, and potential for further code execution depending on server configuration. Confidentiality, integrity, and availability are all rated High impact, making this a significant risk for any WordPress site running the affected theme (Patchstack).

Exploitability

As of the time of publication, no public proof-of-concept exploit code has been identified, and there is no evidence of active in-the-wild exploitation. The EPSS score is approximately 0.0015 (0.15%), indicating a currently low probability of exploitation in the near term. No threat actor attribution has been made, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. However, Patchstack rates this as high priority, noting that vulnerabilities of this class are frequently used in mass-exploit campaigns targeting WordPress sites (Patchstack).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites using the DetailX theme (version ≤ 1.10.0) via passive fingerprinting tools such as WPScan, Shodan, or by inspecting HTTP response headers and page source for theme indicators.
  2. Identify vulnerable parameter: Locate the theme's file inclusion endpoint or parameter that accepts user-controlled input for PHP include/require operations — typically a query parameter or POST field passed to a template loader.
  3. Craft LFI payload: Construct a request with a path traversal payload (e.g., ../../../../wp-config.php or /etc/passwd) in the vulnerable parameter to reference a target local file.
  4. Send malicious request: Submit the crafted HTTP request to the target WordPress site without authentication.
  5. Retrieve sensitive data: If successful, the server returns the contents of the included file (e.g., database credentials from wp-config.php), which can be used for further compromise such as database access or privilege escalation (Patchstack).

Indicators of compromise

  • Network: Unusual HTTP GET or POST requests to WordPress theme endpoints containing path traversal sequences (e.g., ../, ..%2F, %2e%2e%2f) in query parameters or POST body fields.
  • Logs: Web server access logs showing requests with encoded or plaintext directory traversal strings targeting theme-related URLs; HTTP 200 responses to requests containing file path patterns like wp-config.php or /etc/passwd.
  • File System: No direct file system artifacts expected from read-only LFI, but monitor for unexpected file reads of sensitive files (e.g., wp-config.php, /etc/passwd) via server-side logging or file integrity monitoring.
  • Process: Unexpected PHP process activity reading files outside the WordPress web root, detectable via auditd or similar OS-level auditing tools.

Mitigation and workarounds

As of the publication date, no official patch from AncoraThemes is available for the DetailX theme. Patchstack has issued a virtual patching/mitigation rule for its subscribers to block exploitation attempts until an official fix is released. Site owners should consider temporarily disabling or replacing the DetailX theme if an update is not available. Additional hardening measures include implementing strict input validation for file inclusion, using allowlists for permitted file paths, applying least-privilege principles to the web server process, and monitoring for unauthorized file access attempts. Upgrading to a version newer than 1.10.0 is recommended once a patched release becomes available (Patchstack).

Additional resources


SourceThis report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-77115HIGH7.1
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-77116MEDIUM4.3
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-14853MEDIUM4.3
  • woocommerce-bookings
NoYesAug 23, 2026
CVE-2026-77003LOW2.7
  • content-mask
NoYesAug 23, 2026
CVE-2026-13598NONEN/A
  • restrictmate
NoYesAug 23, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management