Klamra Paycal for Aspaclaria <= 1.1.4 - Insecure Direct Object Reference to Authenticated (Subscriber+) Sensitive Information Exposure via 'invoice_id' Parameter
Strategic Overview
- Status
- Patched in 1.1.5
- Affected Plugin
- Klamra Paycal for Aspaclaria
- Affected Version
<= 1.1.4- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-8611
At a glance
CVE-2026-8611 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Klamra Paycal for Aspaclaria WordPress plugin, affecting versions <= 1.1.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.1.5; sites on affected versions should update now. Disclosed June 2026, reported by KEVIN LEE (crattack).
Vulnerability Overview
The Klamra Paycal for Aspaclaria plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.1.4 via the 'invoice_id' parameter due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to download arbitrary customer invoices by enumerating sequential post IDs, exposing sensitive billing PII including full name, email address, phone number, order total, line items, and customer notes belonging to other customers.
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.
CWE-639: Authorization Bypass Through User-Controlled Key
Klamra Paycal for Aspaclaria <= 1.1.4 carries this weakness at invoice_id, and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Klamra Paycal for Aspaclaria the fix is 1.1.5: builds <= 1.1.4 are affected, anything from 1.1.5 onward is not.
Remediation
Update to version 1.1.5, 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: Klamra Paycal for Aspaclaria 1.1.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C