Frisbii Pay <= 1.8.2 - Authenticated (Contributor+) Privilege Escalation
Strategic Overview
- Status
- Patched in 1.8.2.1
- Affected Plugin
- Frisbii Pay
- Affected Version
<= 1.8.2- CVSS
- 8.8High
- Weakness type
- CWE-266 · Incorrect Privilege Assignment
- CVE
CVE-2026-56038
At a glance
CVE-2026-56038 is a high-severity Incorrect Privilege Assignment vulnerability in the Frisbii Pay WordPress plugin, affecting versions <= 1.8.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.8.2.1; sites on affected versions should update now. Disclosed June 2026, reported by Denver Jackson.
Vulnerability Overview
The Frisbii Pay plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.8.2. This makes it possible for authenticated attackers, with Contributor-level access and above, to elevate their privileges.
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 confidentiality, integrity, availability — full site compromise territory.
CWE-266: Incorrect Privilege Assignment
A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.
Remediation
Update to version 1.8.2.1, 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.2.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C