CVE-2026-127132: GamiPress <= 8.1.3 - Authenticated (Subscriber+) SQL Injection via 'name-1[compare]' Parameter
The GamiPress – Gamification plugin to reward points, badges & ranks in WordPress, now with AI plugin for WordPress is vulnerable to generic SQL Injection via the 'name-1[compare]' parameter in all versions up to, and including, 8.1.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires that an administrator has published at least one GamiPress achievement step triggered by a Forminator field-value submission event, as the GamiPress Forminator integration listener is the only path that routes a form submission's raw field array — including the attacker-controlled compare operator — into gamipressquerylogs().
Affected Software
Event History
Frequently Asked Questions
Who is exposed to exploitation?
Sites running GamiPress 8.1.3 or earlier are exposed only if they have at least one published GamiPress achievement step triggered by a Forminator field-value submission event. An attacker must also be able to authenticate to the WordPress site with a Subscriber-level account or higher.
Is the default plugin installation affected?
Not necessarily. The vulnerable path requires the specific GamiPress Forminator integration configuration: a published achievement step using a Forminator field-value submission trigger.
What can an attacker obtain through this issue?
A qualifying authenticated attacker can inject SQL into an existing query and use it to extract sensitive information from the WordPress database. The provided data does not indicate integrity or availability impact.
What can be done if updating is not immediately possible?
Remove or unpublish GamiPress achievement steps that are triggered by Forminator field-value submissions, which removes the only described path that passes the attacker-controlled parameter into the vulnerable query. Restricting or removing untrusted Subscriber-level and higher accounts also reduces exposure.