dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-57635

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges 8 weeks old

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
Unauthenticated Cross Site Request Forgery (CSRF) in FunnelKit Payment Gateway for Stripe WooCommerce <= 1.14.0.3 versions.

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

Unauthenticated Cross-Site Request Forgery (CSRF) vulnerability in FunnelKit Payment Gateway for Stripe WooCommerce plugin versions 1.14.0.3 and earlier allows attackers to trick authenticated users into performing unintended actions (such as modifying payment settings or processing unauthorized transactions) by leveraging the lack of anti-CSRF tokens (nonces) on sensitive form submissions.

MitigationUpdate FunnelKit Payment Gateway for Stripe to the latest version (beyond 1.14.0.3) which should include proper nonce validation; if no update is available, consider disabling the plugin until a patch is released.

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

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

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 FunnelKit Stripe plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and search for 'FunnelKit Payment Gateway for Stripe' or 'FunnelKit Stripe'
    Affected if The plugin appears in the installed plugins list
  2. Check installed version number
    In the plugins list, locate the version number displayed beneath the plugin name, or open the plugin's main PHP file and look for the 'Version' header in the plugin comment block
    Affected if Version is 1.14.0.3 or earlier (any version up to and including 1.14.0.3)
  3. Verify plugin is active
    In WordPress admin > Plugins, check if the plugin shows as 'Active' rather than 'Inactive'
    Affected if Plugin status is Active
  4. Check for unauthorized configuration changes
    Review WooCommerce > Settings > Payments (or FunnelKit settings) for any unexpected modifications to payment gateway configurations, API keys, or webhook URLs
    Affected if Settings have been changed without your knowledge or show unexpected values
  5. Audit admin user accounts
    Navigate to WordPress Users panel and verify that only expected administrator accounts exist, particularly any created recently with suspicious email addresses
    Affected if Unknown or unauthorized admin accounts are present

A user is affected if the FunnelKit Payment Gateway for Stripe plugin is installed, active, and running version 1.14.0.3 or earlier.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update FunnelKit Payment Gateway for Stripe to the latest version (beyond 1.14.0.3) which should include proper nonce validation; if no update is available, consider disabling the plugin until a patch is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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