Quick answers
- Is CVE-2025-69168 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-69168 being exploited in the wild.
- How severe is CVE-2025-69168?
- High severity, with a CVSS score of 8.1, published 17 June 2026.
- Which products and versions are affected?
- ThemeREX Spike <= 1.2.
- Is there a fix for CVE-2025-69168?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-69168 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2025-69168?
- Check whether you run ThemeREX Spike at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Local File Inclusion (LFI) vulnerability exists in the ThemeREX Spike theme for WordPress through version 1.2. The flaw stems from improper control of filenames used in PHP include or require statements (CWE-98), allowing an unauthenticated remote attacker to include arbitrary files from the local file system. While the attack complexity is rated as high, a successful exploit could allow the attacker to read sensitive system files (such as wp-config.php) or execute code if they can upload or find a controllable file on the server. As of the advisory date, no official patch is available, and users are encouraged to use third-party mitigation rules.
Affected products
- ThemeREX Spike <= 1.2
Timeline
- 2025-11-09: other: Vulnerability reported by researcher Bonds
- 2026-05-27: disclosed: Vulnerability details published by Patchstack
- 2026-06-17: advisory: CVE published in NVD