Quick answers
- Is CVE-2026-15439 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15439 being exploited in the wild.
- How severe is CVE-2026-15439?
- Medium severity, with a CVSS score of 6.5, published 11 September 2026.
- Which products and versions are affected?
- GamiPress up to and including 7.9.7.
- Is there a fix for CVE-2026-15439?
- 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-2026-15439 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-15439?
- Check whether you run GamiPress 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 vulnerability is a boolean-based SQL injection in the 'q' parameter of the gamipress_wpforo_get_posts AJAX action. The vulnerable code passes user input through $wpdb->esc_like() but then directly interpolates it into a single-quoted LIKE clause without using $wpdb->prepare() with %s placeholders. Because esc_like() doubles backslashes after WordPress magic quotes, an attacker can inject a backslash-quote sequence that MySQL interprets as a literal backslash followed by a closing quote, breaking out of the LIKE clause. The attack requires an authenticated Subscriber account (the lowest user role) and a valid gamipress_admin nonce that is exposed on all WordPress admin pages. The wpForo plugin must be active to register the vulnerable AJAX callback, but no wpForo-specific vulnerability is exploited. Patches should use proper parameterized queries with $wpdb->prepare().
Affected products
- GamiPress GamiPress up to and including 7.9.7
Timeline
- 2026-09-11: disclosed