dbcve.org
GamipressWordPress extension

CVE-2023-25697

MEDIUM · 6.3 CVSS v3.1 Published 2024-06-19
Fix available
A fix is available. Upgrade to 2.5.7 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in GamiPress.This issue affects GamiPress: from n/a through 2.5.6.

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

Cross-Site Request Forgery (CSRF) vulnerability in GamiPress plugin versions up to 2.5.6 allows attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious requests. The vulnerability stems from missing or improper CSRF protections on sensitive actions within the plugin.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing actions and validate these tokens server-side before processing requests. Additionally, implement SameSite cookie attributes and consider adding origin/referer validation.

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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Locate GamiPress plugin installation
    Access your WordPress site via FTP or file manager, navigate to /wp-content/plugins/ and check if a folder named 'gamipress' exists. Alternatively, log into WordPress admin and go to Plugins > Installed Plugins to confirm GamiPress is listed.
    Affected if The gamipress folder exists in /wp-content/plugins/ or the plugin appears in the WordPress admin plugins list.
  2. Verify GamiPress is active
    In WordPress admin, go to Plugins > Installed Plugins and check the status indicator next to GamiPress, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' AND option_value LIKE '%gamipress%';
    Affected if GamiPress is activated and loaded in the active_plugins array.
  3. Determine installed version number
    In WordPress admin, go to Plugins > Installed Plugins and click on GamiPress to view the version number in the plugin header. Alternatively, open /wp-content/plugins/gamipress/gamipress.php in a text editor and locate the 'Version:' header comment near the top of the file.
    Affected if The reported version is less than 2.5.7 (for example, 2.5.6, 2.5.5, etc.).
  4. Identify sensitive actions lacking CSRF protection
    Review GamiPress plugin files in /wp-content/plugins/gamipress/includes/ for form submissions and admin action handlers. Search for state-changing functions (like award-points, add-rank, update-settings) that process $_POST or $_GET requests without verifying wp_verify_nonce() or check_admin_referer() calls. Common files to inspect include ajax-functions.php, admin-functions.php, and shortcodes.php.
    Affected if Sensitive action handlers are found that process requests without nonce validation.

Your environment is affected if GamiPress plugin is active with a version lower than 2.5.7 and contains sensitive actions without CSRF token validation.

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 2.5.7 or later
Fixed in 2.5.7
Interim mitigation

Implement anti-CSRF tokens (nonces) on all state-changing actions and validate these tokens server-side before processing requests. Additionally, implement SameSite cookie attributes and consider adding origin/referer validation.

Recommended fix High confidence

GamiPress 2.5.7

  1. 1. Backup your WordPress site and database before performing any updates.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate GamiPress in the plugins list and check if an update is available.
  4. 4. If an update is available, click 'Update Now' to update to the latest version.
  5. 5. Alternatively, you can manually download GamiPress 2.5.7 or later from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the version number matches 2.5.7 or higher in the plugins list.
  7. 7. Test critical GamiPress functionality (points, achievements, ranks) to ensure the update didn't break existing functionality.

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

Fix this in Gamipress Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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