CVE-2026-32420
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Ruben Garcia GamiPress gamipress allows Cross Site Request Forgery.This issue affects GamiPress: from n/a through <= 7.6.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 confidenceCross-Site Request Forgery (CSRF) vulnerability in GamiPress WordPress plugin allows remote attackers to trick authenticated users into submitting unintended state-changing requests. The plugin lacks proper anti-CSRF token validation on sensitive actions.
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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm GamiPress plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and locate GamiPress. Note the version number displayed.Affected if GamiPress plugin is not installed or is inactive
-
Identify installed GamiPress versionNavigate to Plugins > Installed Plugins, find GamiPress, and record the version number shown (e.g., displayed as 'Version 6.x.x' or similar).Affected if Version cannot be determined or no version is displayed
-
Check for nonce verification in plugin codeAccess the GamiPress plugin directory via file manager or FTP. Search PHP files for 'wp_verify_nonce' or 'check_admin_referer' functions. Focus on files handling user actions (e.g., ajax-handlers.php, functions.php, or any file processing form submissions).Affected if State-changing actions (like awarding points, unlocking achievements, or modifying user ranks) do NOT contain wp_verify_nonce or check_admin_referer calls
-
Inspect AJAX request handlers for CSRF protectionIn the plugin directory, examine AJAX-related files (typically in /includes/ajax/ or containing 'add_action("wp_ajax_' hooks). Verify each handler includes nonce verification before processing the request.Affected if AJAX endpoints that modify data (create, update, delete operations) lack nonce validation logic
-
Review form submissions for nonce fieldsCheck plugin templates and form handlers for presence of wp_nonce_field in HTML forms, especially those performing privileged actions like user management, points adjustment, or settings changes.Affected if Forms that perform state-changing operations do not generate or verify nonce tokens
If GamiPress is installed and its code lacks proper nonce verification (wp_verify_nonce or wp_nonce_field) on sensitive actions or AJAX handlers, the environment is affected by this CSRF vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement WordPress nonces (wp_verify_nonce) on all state-changing form submissions and AJAX requests within the plugin to verify the request originates from legitimate user sessions.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32420 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32420 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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