CVE-2026-121792 json
GamiPress <= 8.1.1 - Authenticated (Subscriber+) SQL Injection via 'Gravity Forms Name/List Field' Parameter
published 2d ago modified yesterday also EUVD-2026-118971
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 20%
- public exploits
- 0
- none known
Summary
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 'input_<field_id>.<part> (Gravity Forms name-field part, or list-field row)' parameter in all versions up to, and including, 8.1.1 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 a GamiPress achievement already configured against a Gravity Forms 'field value submission' event with the corresponding form published — a standard setup for sites using the integration.
Is CVE-2026-121792 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- rubengc GamiPress – Gamification plugin to reward points, badges & ranks in WordPress, now with AI
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/9fa05058-3c16-4e61-bd6a-a1a09d2f56cc?source=cve
- plugins.trac.wordpress.org /browser/gamipress/tags/8.1.1/includes/functions/logs.php#L326
- plugins.trac.wordpress.org /browser/gamipress/tags/8.1.1/includes/functions/logs.php#L386
- plugins.trac.wordpress.org /browser/gamipress/tags/8.1.1/integrations/gravity-forms/includes/triggers.php#L256
- plugins.trac.wordpress.org /browser/gamipress/tags/8.1.1/integrations/gravity-forms/includes/listeners.php#L126
- plugins.trac.wordpress.org /browser/gamipress/tags/8.1.1/integrations/gravity-forms/includes/listeners.php#L65
- plugins.trac.wordpress.org /changeset?reponame=&old=3787551%40gamipress&new=3787551%40gamipress
Sources
- CVE List CVE-2026-121792
- NVD CVE-2026-121792
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.