dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-13450

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The GamiPress WordPress plugin up to version 7.9.4 contains an Insecure Direct Object Reference (IDOR) vulnerability via the 'access' parameter. Due to missing server-side validation on a user-controlled key, unauthenticated attackers can view private activity log entries (badge earnings, points changes, event records from WooCommerce, LearnDash, BuddyPress). The required nonce is exposed to all frontend users via wp_localize_script, trivially bypassing the authentication barrier.

MitigationUpdate to the latest GamiPress version once a patch is released. Until then, consider restricting access to the affected endpoints via web server configuration or implementing interim access control validation on the 'access' parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify GamiPress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for GamiPress, or check the /wp-content/plugins/gamipress directory exists on the server
    Affected if GamiPress plugin is present on the WordPress site
  2. Check installed GamiPress version
    In WordPress admin, go to Plugins > Installed Plugins > GamiPress and view the version number, or check the version in gamipress.php file header
    Affected if Version is 7.9.4 or lower
  3. Confirm activity log feature is enabled
    Navigate to GamiPress > Settings > Activity Log and verify the 'Enable activity log' option is checked, or check if any activity logs exist in wp_posts or custom tables
    Affected if Activity logging is enabled and log entries exist
  4. Detect exposed nonce via wp_localize_script
    View page source of any frontend page and search for 'gamiPress' or 'gamipress' in wp_localize_script data. Look for a nonce value assigned to a variable that should require higher privileges
    Affected if A valid nonce is exposed in frontend JavaScript variables accessible to unauthenticated users
  5. Test access parameter for IDOR
    Send a GET request to the activity log endpoint (typically /wp-admin/admin-ajax.php?action=gamipress_get_activity_log or similar) with an arbitrary 'access' parameter value, without authentication
    Affected if The endpoint returns activity log data without requiring authentication or proper authorization

A site is affected if it runs GamiPress 7.9.4 or lower with activity logging enabled, and the activity log endpoint can be accessed or the nonce is exposed to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest GamiPress version once a patch is released. Until then, consider restricting access to the affected endpoints via web server configuration or implementing interim access control validation on the 'access' parameter.

Recommended fix High confidence

GamiPress 7.9.5 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the GamiPress plugin
  4. Check the current version (should be 7.9.4 or earlier)
  5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  7. After updating, verify the version number reflects the new release

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13450 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13450 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data