dbcve.org
GamipressWordPress extension

CVE-2024-11036

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-19
Fix available
A fix is available. Upgrade to 7.1.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 The GamiPress – The #1 gamification plugin to reward points, achievements, badges & ranks in WordPress plugin for WordPress is vulnerable to arbitrary shortcode execution via gamipress_get_user_earnings AJAX action in all versions up to, and including, 7.1.5. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.

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.1.5 contains an arbitrary shortcode execution vulnerability in the gamipress_get_user_earnings AJAX action. The action fails to properly validate user-supplied input before passing it to the do_shortcode() function, allowing unauthenticated attackers to execute arbitrary shortcodes on the WordPress site.

MitigationUpdate GamiPress to version 7.1.6 or later which contains the patch for proper input validation. If immediate update is not possible, consider disabling the plugin or implementing Web Application Firewall (WAF) rules to block the vulnerable AJAX endpoint.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GamipressWordPress extension
Affected:< 7.1.6

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
High
Integrity
High
Availability
High

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

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. Confirm GamiPress plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'GamiPress' in the plugin list.
    Affected if GamiPress plugin is present in the plugins list
  2. Check installed GamiPress version
    In Plugins list, click on GamiPress to view plugin details, or check the plugin file header in wp-content/plugins/gamipress/gamipress.php for the 'Version' comment.
    Affected if Version is less than 7.1.6 (for example 7.1.5, 7.1.4, etc.)
  3. Verify AJAX endpoint is accessible
    Send a request to your-site.com/wp-admin/admin-ajax.php?action=gamipress_get_user_earnings using curl or browser devtools. A response other than 0 or403 indicates the endpoint exists.
    Affected if The endpoint returns a valid response (not 0 or error) indicating the action is registered and callable
  4. Test shortcode execution capability
    Send a POST request to admin-ajax.php with action=gamipress_get_user_earnings and a shortcode in a parameter (such as shortcode: '[shortcode]'). Check if the shortcode is processed in the response.
    Affected if The response contains rendered shortcode output, confirming do_shortcode() processes unsanitized input

Your environment is affected if GamiPress version is below 7.1.6 and the gamipress_get_user_earnings AJAX endpoint responds to unauthenticated requests.

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
Upgrade available Upgrade to 7.1.6 or later
Fixed in 7.1.6
Interim mitigation

Update GamiPress to version 7.1.6 or later which contains the patch for proper input validation. If immediate update is not possible, consider disabling the plugin or implementing Web Application Firewall (WAF) rules to block the vulnerable AJAX endpoint.

Recommended fix High confidence

GamiPress 7.1.6

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find GamiPress in the plugin list
  4. If an update is available, click 'Update Now' to update to version 7.1.6 or later
  5. Alternatively, navigate to Dashboard > Updates and select GamiPress to update
  6. Verify the update completed successfully by checking the plugin version

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

Fix this in Gamipress Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11036 — 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-2024-11036 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