CVE-2026-15439: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in rubengc GamiPress – Gamification plugin to reward points, badges & ranks in WordPress, now with AI
The GamiPress plugin for WordPress is vulnerable to authenticated (Subscriber+) SQL Injection via the 'q' parameter of the wpForo integration AJAX selector (action gamipress_wpforo_get_posts) in versions up to, and including, 7.9.7. The value is passed only through $wpdb->esc_like() and interpolated directly into a single-quoted LIKE clause with no %s placeholder. Because esc_like() runs after WordPress core magic quotes, it doubles the injected backslash (\' -> \\'), which MySQL reads as one literal backslash followed by a live closing quote, allowing the attacker to break out of the string and inject boolean-based SQL. The wpForo plugin only needs to be active to register the callback; no wpForo vulnerability is used. Requires a Subscriber account, which can read the gamipress_admin nonce (exposed on every admin page, e.g. /wp-admin/profile.php). Note: the researcher's Simple:Press vectors (PoC 2 & 3) do not reproduce in current code, which uses $wpdb->prepare() with %s placeholders; only the wpForo selector is confirmed.
AI Analysis
Technical Summary
CVE-2026-15439 describes an authenticated SQL Injection vulnerability in the GamiPress plugin for WordPress, affecting versions up to and including 7.9.7. The vulnerability exists in the 'q' parameter of the wpForo integration AJAX selector (action gamipress_wpforo_get_posts). Input is sanitized only with $wpdb->esc_like() and interpolated directly into a single-quoted LIKE clause without using %s placeholders in $wpdb->prepare(). Due to WordPress core magic quotes and the behavior of esc_like(), an attacker can inject SQL by breaking out of the string context, enabling boolean-based SQL injection. Exploitation requires a Subscriber account and the wpForo plugin to be active, but no vulnerabilities in wpForo itself are exploited. The vulnerability does not affect Simple:Press integration, which uses proper $wpdb->prepare() calls.
Potential Impact
An authenticated user with Subscriber privileges can perform SQL Injection attacks against the WordPress database via the vulnerable 'q' parameter. This can lead to unauthorized data disclosure (confidentiality impact) without affecting integrity or availability. The vulnerability allows reading sensitive information such as the gamipress_admin nonce, which is exposed on admin pages. There is no indication of remote unauthenticated exploitation or active exploitation in the wild.
Mitigation Recommendations
No official patch or fix is explicitly stated in the provided data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict Subscriber-level access where possible and monitor for updates from the vendor. Avoid enabling the wpForo integration if not required. Do not rely on the wpForo plugin being secure as it is not the source of the vulnerability.
CVE-2026-15439: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in rubengc GamiPress – Gamification plugin to reward points, badges & ranks in WordPress, now with AI
Description
The GamiPress plugin for WordPress is vulnerable to authenticated (Subscriber+) SQL Injection via the 'q' parameter of the wpForo integration AJAX selector (action gamipress_wpforo_get_posts) in versions up to, and including, 7.9.7. The value is passed only through $wpdb->esc_like() and interpolated directly into a single-quoted LIKE clause with no %s placeholder. Because esc_like() runs after WordPress core magic quotes, it doubles the injected backslash (\' -> \\'), which MySQL reads as one literal backslash followed by a live closing quote, allowing the attacker to break out of the string and inject boolean-based SQL. The wpForo plugin only needs to be active to register the callback; no wpForo vulnerability is used. Requires a Subscriber account, which can read the gamipress_admin nonce (exposed on every admin page, e.g. /wp-admin/profile.php). Note: the researcher's Simple:Press vectors (PoC 2 & 3) do not reproduce in current code, which uses $wpdb->prepare() with %s placeholders; only the wpForo selector is confirmed.
CVSS v3.1
Score 6.5medium
Affected software
rubengc
GamiPress – Gamification plugin to reward points, badges & ranks in WordPress, now with AI
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-15439 describes an authenticated SQL Injection vulnerability in the GamiPress plugin for WordPress, affecting versions up to and including 7.9.7. The vulnerability exists in the 'q' parameter of the wpForo integration AJAX selector (action gamipress_wpforo_get_posts). Input is sanitized only with $wpdb->esc_like() and interpolated directly into a single-quoted LIKE clause without using %s placeholders in $wpdb->prepare(). Due to WordPress core magic quotes and the behavior of esc_like(), an attacker can inject SQL by breaking out of the string context, enabling boolean-based SQL injection. Exploitation requires a Subscriber account and the wpForo plugin to be active, but no vulnerabilities in wpForo itself are exploited. The vulnerability does not affect Simple:Press integration, which uses proper $wpdb->prepare() calls.
Potential Impact
An authenticated user with Subscriber privileges can perform SQL Injection attacks against the WordPress database via the vulnerable 'q' parameter. This can lead to unauthorized data disclosure (confidentiality impact) without affecting integrity or availability. The vulnerability allows reading sensitive information such as the gamipress_admin nonce, which is exposed on admin pages. There is no indication of remote unauthenticated exploitation or active exploitation in the wild.
Mitigation Recommendations
No official patch or fix is explicitly stated in the provided data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict Subscriber-level access where possible and monitor for updates from the vendor. Avoid enabling the wpForo integration if not required. Do not rely on the wpForo plugin being secure as it is not the source of the vulnerability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-07-10T18:24:33.819Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aa41f3091cc7f384856d44d
Added to database: 09/11/2026, 15:33:04 UTC
Last enriched: 09/11/2026, 15:48:27 UTC
Last updated: 09/11/2026, 22:23:25 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.