GamiPress <= 2.5.6 - Cross-Site Request Forgery to User Earnings Deletion
Strategic Overview
- Status
- Patched in 2.5.7
- Affected Plugin
- GamiPress – Gamification plugin to reward points, badges & ranks in WordPress, now with AI
- Affected Version
<= 2.5.6- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-25697
At a glance
CVE-2023-25697 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the GamiPress WordPress plugin, affecting versions <= 2.5.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.5.7; sites on affected versions should update now. Disclosed February 2023, reported by Dave Jong.
Vulnerability Overview
The GamiPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.5.6. This is due to missing or incorrect nonce validation on the bulk_delete function. This makes it possible for unauthenticated attackers to invoke this function via forged request granted they can trick a site administrator into performing an action such as clicking on a link and results in the bulk deletion of user earnings.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in GamiPress <= 2.5.6 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For GamiPress the fix is 2.5.7: builds <= 2.5.6 are affected, anything from 2.5.7 onward is not.
Remediation
Update to version 2.5.7, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to GamiPress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: GamiPress 2.5.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in GamiPress – Gamification plugin to reward points, badges & ranks in WordPress, now with AI
- 9.8CVE-2023-24000: GamiPress <= 2.5.7 SQL Injection
CVE-2023-24000 - 8.8CVE-2025-47508: GamiPress <= 7.3.7 Local File Inclusion
CVE-2025-47508 - 8.8CVE-2024-1799: GamiPress SQL Injection
CVE-2024-1799 - 7.5CVE-2026-59538: GamiPress SQL Injection
CVE-2026-59538 - 7.5CVE-2024-13496: GamiPress <= 7.3.1 SQL Injection
CVE-2024-13496 - 7.3CVE-2024-13499: GamiPress <= 7.2.1 Arbitrary Shortcode Execution
CVE-2024-13499 - 7.3CVE-2024-13495: GamiPress <= 7.2.1 Arbitrary Shortcode Execution
CVE-2024-13495 - 7.3CVE-2024-11036: GamiPress Arbitrary Shortcode Execution
CVE-2024-11036
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C