Frisbii Pay <= 1.8.9 - Missing Authorization to Authenticated (Subscriber+) Payment Token Modification
Strategic Overview
- Status
- Patched in 1.8.10
- Affected Plugin
- Frisbii Pay
- Affected Version
<= 1.8.9- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-3462
At a glance
CVE-2026-3462 is a medium-severity Missing Authorization vulnerability in the Frisbii Pay WordPress plugin, affecting versions <= 1.8.9. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.8.10; sites on affected versions should update now. Disclosed June 2026, reported by momopon1415.
Vulnerability Overview
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 Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on integrity.
CWE-862: Missing Authorization
Frisbii Pay <= 1.8.9 carries this weakness at upload_csv, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Frisbii Pay the fix is 1.8.10: builds <= 1.8.9 are affected, anything from 1.8.10 onward is not.
Remediation
Update to version 1.8.10, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Frisbii Pay 1.8.10 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Frisbii Pay
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C