Frisbii Pay · Security record
Is Frisbii Pay safe?
One known vulnerability affects the current version (1.8.21), and it has no fix yet.
Checked 2 days ago against the WPVulnerability database, for version 1.8.21.
How it’s looked after
- Last release
- Oct 31, 2026 (1 week ago)
- Releases in the last year
- 23
- Tested up to
- WordPress 7.1.4
- Support resolved
- 0 of 1 threads in two months
- Active installs
- 1K+
4 known vulnerabilities
- 2 high
- 2 medium
1 affects the current version. 1 has no fix yet.
Disclosed each year
- 20251
- 20263
Every known vulnerability in Frisbii Pay
Newest first, with any that affect the current version at the top.
Affects the current version · No fix yet · CVE-2026-118076 · Jun 26, 2026 · Wordfence
Fixed in 1.8.10 · CVE-2026-3462 · Jun 26, 2026 · Wordfence
Fixed in 1.8.2.1 · CVE-2026-56038 · Jun 24, 2026 · Wordfence
- medium
Missing Authorization
Fixed in 1.8.3 · CVE-2025-58616 · Sep 3, 2025 · Wordfence
Questions about Frisbii Pay’s security
Is Frisbii Pay safe to use?
Yes: 1 known vulnerability affects version 1.8.21, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.
Does Frisbii Pay have known security vulnerabilities?
Yes: 1 known vulnerability affects version 1.8.21, according to WPVulnerability’s database.
Is Frisbii Pay still maintained?
Yes. Its last release was 1 week ago. Its authors resolved 0 of the 1 support threads opened in the last two months.
Is Frisbii Pay compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.