PatchSiren cyber security CVE debrief
CVE-2026-15439 rubengc CVE debrief
The GamiPress plugin for WordPress, up to and including version 7.9.7, is vulnerable to authenticated SQL Injection via the 'q' parameter of the wpForo integration AJAX selector (action gamipress_wpforo_get_posts). An attacker with a Subscriber account can exploit this by injecting boolean-based SQL, breaking out of the string and injecting SQL, due to the value being passed through $wpdb->esc_like() and interpolated directly into a single-quoted LIKE clause without a %s placeholder. This issue arises because the wpForo plugin only needs to be active to register the callback; no wpForo vulnerability is used. The vulnerability requires a Subscriber account, which can read the gamipr
- Vendor
- rubengc
- Product
- GamiPress – Gamification plugin to reward points, badges & ranks in WordPress, now with AI
- CVSS
- MEDIUM 6.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-11
- Original CVE updated
- 2026-09-11
- Advisory published
- 2026-09-11
- Advisory updated
- 2026-09-11
Who should care
Defenders managing WordPress installations with the GamiPress plugin and wpForo integration should assess exposure and potential impact. Prioritization is recommended for environments with Subscriber account management and wpForo configurations.
Why it matters
CVE-2026-15439 is a SQL injection vulnerability in the GamiPress plugin for WordPress, exploitable by authenticated Subscribers. Defenders should verify exposure, assess impact, and prioritize configurations and monitoring.
- Potential for data exposure through SQL injection
- Need for validation of Subscriber account configurations
- Importance of monitoring for potential SQL injection attempts
- Verification of wpForo integration settings and input parameters
Technical summary
The GamiPress plugin for WordPress, up to and including version 7.9.7, is vulnerable to authenticated SQL Injection via the 'q' parameter of the wpForo integration AJAX selector (action gamipress_wpforo_get_posts). An attacker with a Subscriber account can exploit this by injecting boolean-based SQL, breaking out of the string and injecting SQL, due to the value being passed through $wpdb->esc_like() and interpolated directly into a single-quoted LIKE clause without a %s placeholder.
Defensive priority
Defenders should prioritize verifying exposure and assessing potential impact, focusing on Subscriber account management and wpForo integration configurations.
Recommended defensive actions
- Verify Subscriber account configurations and ensure proper management.
- Assess wpForo integration settings and validate input parameters.
- Implement additional monitoring for potential SQL injection attempts.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
Evidence notes
The vulnerability was discovered in the GamiPress plugin for WordPress, specifically in the wpForo integration AJAX selector. The issue arises from the 'q' parameter being passed through $wpdb->esc_like() and interpolated directly into a single-quoted LIKE clause without a %s placeholder.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-15439 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-15439
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-15439 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-15439
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/gamipress/tags/7.9.3/integrations/wpforo/includes/functions.php
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.