dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3462

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 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
The Frisbii Pay plugin for WordPress is vulnerable to unauthorized modification of data due to missing capability checks on the 'upload_csv' and 'process_batch' functions in all versions up to, and including, 1.8.9. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary CSV data and overwrite WooCommerce payment tokens, postmeta, and order meta records.

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

The Frisbii Pay WordPress plugin lacks capability checks on the 'upload_csv' and 'process_batch' functions, allowing any authenticated user with Subscriber-level access or higher to upload arbitrary CSV data. This enables attackers to overwrite WooCommerce payment tokens and modify postmeta/order meta records.

MitigationUpdate to version 1.9.0 or later which includes proper capability checks. Until then, consider disabling the plugin or restricting user registration.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify Frisbii Pay plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Frisbii Pay' in the list. Alternatively, check the file system at /wp-content/plugins/ for a folder containing 'frisbii' or 'frisbii-pay'.
    Affected if The Frisbii Pay plugin is installed and active on the WordPress site.
  2. Check installed plugin version
    In WordPress admin_plugins list, find Frisbii Pay and note the version number displayed. Alternatively, read the main plugin PHP file header for 'Version:' or check the plugin folder for a readme.txt/changelog with version info. Compare the version to 1.9.0.
    Affected if The installed version is lower than 1.9.0 (for example, 1.8.x, 1.7.x, etc.).
  3. Confirm WooCommerce is present
    Check if WooCommerce plugin is installed and active by reviewing the plugins list, or check for WooCommerce tables in the database (typically wp_woocommerce_payment_tokens if the database prefix is wp_).
    Affected if WooCommerce is installed, as the vulnerability specifically targets WooCommerce payment tokens.
  4. Identify user roles with Subscriber-level access or higher
    In WordPress admin, go to Users > All Users and review the roles assigned. Check if any users have 'Subscriber', 'Contributor', 'Author', 'Editor', or 'Administrator' roles. Also check Users > User Roles or use a user role editor plugin to enumerate all existing roles.
    Affected if There is at least one user account with Subscriber-level access or higher, or any user registration is enabled allowing new subscriptions.
  5. Verify plugin AJAX endpoints are accessible
    Check the plugin source code (main PHP file and any ajax-handling files) for registered actions like 'wp_ajax_frisbii_upload_csv' or 'wp_ajax_nopriv_frisbii_upload_csv' and 'wp_ajax_frisbii_process_batch'. Use a directory scan or grep for these action hooks in the plugin folder.
    Affected if The plugin registers AJAX handlers for 'upload_csv' or 'process_batch' without capability checks (no current_user_can() verification before processing).

A user is affected if the Frisbii Pay plugin versions below 1.9.0 is installed, WooCommerce is present, and any authenticated user with Subscriber-level or higher access exists on the site.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 1.9.0 or later which includes proper capability checks. Until then, consider disabling the plugin or restricting user registration.

Recommended fix Moderate confidence

Frisbii Pay plugin version 1.9.0 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Frisbii Pay plugin
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, download the latest version from wordpress.org/plugins and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the version number reflects the latest release (version 1.9.0 or higher)

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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