Quick answers
- Is CVE-2025-69170 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-69170 being exploited in the wild.
- How severe is CVE-2025-69170?
- High severity, with a CVSS score of 8.1, published 17 June 2026.
- Which products and versions are affected?
- ThemeREX Eventicity <= 1.5.
- Is there a fix for CVE-2025-69170?
- 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-69170 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2025-69170?
- Check whether you run ThemeREX Eventicity 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
The Eventicity theme for WordPress (versions <= 1.5) is vulnerable to Local File Inclusion (LFI) due to improper control of filenames passed to PHP include/require statements (CWE-98). An unauthenticated remote attacker can exploit this by sending specially crafted requests to include local files from the server's filesystem. Successful exploitation can lead to the disclosure of sensitive information, such as the wp-config.php file containing database credentials, or potentially remote code execution if the attacker can upload or influence the content of a local file. As of the advisory date, no official patch has been released, and users are advised to use third-party security rules or migrate to a supported theme.
Affected products
- ThemeREX Eventicity <= 1.5
Timeline
- 2025-11-09: other: Vulnerability reported by researcher Bonds
- 2026-05-27: advisory: Patchstack published advisory details
- 2026-06-17: disclosed: CVE published to NVD