dbcve.org
GamipressWordPress extension

CVE-2023-24000

CRITICAL · 9.8 CVSS v3.1 Published 2023-10-31
Fix available
A fix is available. Upgrade to after 2.5.7 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in GamiPress gamipress allows SQL Injection.This issue affects GamiPress: from n/a through 2.5.7.

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 · moderate confidence

SQL Injection vulnerability in the GamiPress WordPress plugin allows attackers to inject malicious SQL commands via unsanitized input, potentially enabling data exfiltration, privilege escalation, or complete database compromise.

MitigationUpgrade GamiPress to the patched version. If immediate update is not possible, disable the plugin or implement WAF rules to block SQL injection attack patterns.

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:<= 2.5.7

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. Verify GamiPress plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins. Look for 'GamiPress' in the list, or check the wp-content/plugins/gamipress/ directory exists on the server.
    Affected if GamiPress plugin is present on the WordPress site
  2. Confirm GamiPress version number
    In WordPress admin, go to Plugins > Installed Plugins and click on GamiPress to view the version, or open /wp-content/plugins/gamipress/readme.txt and check the 'Stable tag' line, or inspect the main plugin PHP file header.
    Affected if Version is 2.5.7 or lower (e.g., 2.5.6, 2.5.5, etc.)
  3. Verify plugin is active
    In WordPress admin > Plugins > Installed Plugins, confirm the GamiPress plugin has 'Active' status under the plugin name.
    Affected if Plugin is currently active and processing requests
  4. Check for unauthorized database activity
    Review WordPress debug logs (wp-content/debug.log if logging is enabled), server access logs, and database logs for unusual SQL syntax or patterns in query strings that may indicate exploitation attempts.
    Affected if Suspicious SQL patterns found in logs referencing GamiPress-related URLs or parameters

A site is affected if GamiPress version 2.5.7 or lower is installed, active, and processing user-supplied input that could contain SQL injection payloads.

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 a release after 2.5.7
Interim mitigation

Upgrade GamiPress to the patched version. If immediate update is not possible, disable the plugin or implement WAF rules to block SQL injection attack patterns.

Recommended fix High confidence

GamiPress 2.5.8 or later (latest stable release)

  1. 1. Back up your WordPress site database and files before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Find GamiPress in the plugin list.
  4. 4. If there is an update available, click 'Update Now' to update to the latest version.
  5. 5. Alternatively, you can download the latest version from the official WordPress plugin repository and upload it manually.
  6. 6. After updating, verify the plugin is running version 2.5.8 or higher.
  7. 7. Test critical user engagement functionality (points, achievements, ranks, logs) to ensure the update did not break existing features.
Caveat Minor version updates typically do not include breaking changes; always test on staging first

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

Fix this in Gamipress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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