CVE-2026-25337
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 wpcoachify Coachify coachify allows Cross Site Request Forgery.This issue affects Coachify: from n/a through <= 1.1.5.
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 the Coachify WordPress plugin allows attackers to trick authenticated users into unknowingly submitting malicious requests, potentially performing unauthorized actions within the plugin's functionality.
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 Coachify plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'Coachify' in the list. Note the installed version displayed.Affected if Coachify plugin is present in the WordPress installation with any version
-
Check for missing nonce verification in plugin codeAccess the WordPress file system via FTP or file manager. Navigate to wp-content/plugins/coachify and search PHP files for 'wp_verify_nonce' or 'check_admin_referer' functions. Use grep or a code editor to find AJAX handlers and form processing code.Affected if Forms or AJAX endpoints in the plugin code lack nonce verification calls (wp_verify_nonce, check_ajax_referer, check_admin_referer)
-
Inspect forms for CSRF token fieldsView page source of any Coachify frontend or admin forms. Look for input fields named '_wpnonce' or similar nonce field names. Compare against WordPress nonces generated by wp_nonce_field().Affected if Forms rendered by the plugin do not contain hidden nonce token fields
-
Verify AJAX endpoint nonce checksExamine plugin AJAX action handlers (look for 'wp_ajax_' and 'wp_ajax_nopriv_' hooks in plugin PHP files). Confirm each handler calls wp_verify_nonce() or check_ajax_referer() before processing requests.Affected if AJAX endpoints registered by the plugin do not validate nonces before executing state-changing operations
A user is affected if the Coachify plugin is installed and its forms or AJAX endpoints lack nonce verification code, allowing forged requests to execute.
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 anti-CSRF tokens (nonces) on all forms and state-changing AJAX endpoints, and validate the Origin/Referer headers to ensure requests originate from legitimate sources.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-25337 — 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-25337 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