CVE-2026-13450 json
GamiPress <= 7.9.4 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Disclosure via 'access' Parameter
published 4mo ago modified 4mo ago also EUVD-2026-42540
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
The GamiPress – Gamification plugin to reward points, achievements, badges & ranks in WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 7.9.4 via the 'access' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to view private GamiPress activity log entries belonging to any user, including badge earnings, points balance changes, and event records from integrated plugins such as WooCommerce, LearnDash, and BuddyPress. This is exploitable by any unauthenticated visitor because the required 'gamipress' nonce is broadcast to all front-end users via wp_localize_script on the wp_enqueue_scripts hook, making the sole authentication barrier trivially bypassable.
Is CVE-2026-13450 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
- yes
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- rubengc GamiPress – Gamification plugin to reward points, achievements, badges & ranks in WordPress
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/3006261b-a09e-4cff-b49f-49e992c6fe0b?source=cve
- plugins.trac.wordpress.org /browser/gamipress/tags/7.9.3/includes/ajax-functions.php#L51
- plugins.trac.wordpress.org /browser/gamipress/tags/7.9.3/includes/ajax-functions.php#L48
- plugins.trac.wordpress.org /browser/gamipress/tags/7.9.3/includes/shortcodes/gamipress_logs.php#L272
- plugins.trac.wordpress.org /browser/gamipress/tags/7.9.3/includes/shortcodes/gamipress_logs.php#L329
- plugins.trac.wordpress.org /browser/gamipress/tags/7.9.3/includes/ajax-functions.php#L73
- plugins.trac.wordpress.org /browser/gamipress/tags/7.9.3/includes/scripts.php#L51
- plugins.trac.wordpress.org /browser/gamipress/tags/7.8.6/includes/ajax-functions.php#L51
- plugins.trac.wordpress.org /browser/gamipress/tags/7.8.6/includes/ajax-functions.php#L48
- plugins.trac.wordpress.org /browser/gamipress/tags/7.8.6/includes/shortcodes/gamipress_logs.php#L272
- plugins.trac.wordpress.org /browser/gamipress/tags/7.8.6/includes/shortcodes/gamipress_logs.php#L329
- plugins.trac.wordpress.org /browser/gamipress/tags/7.8.6/includes/ajax-functions.php#L73
- plugins.trac.wordpress.org /browser/gamipress/tags/7.8.6/includes/scripts.php#L51
- plugins.trac.wordpress.org /changeset?reponame=&old=3593749%40gamipress&new=3593749%40gamipress
Sources
- CVE List CVE-2026-13450
- NVD CVE-2026-13450
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.