Alkubot – Gamify discounts, sell more and give less at the right time < 3.0.0 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 3.0.0
- Affected Version
< 3.0.0- CVSS
- 7.5High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Alkubot WordPress plugin, affecting versions < 3.0.0. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 3.0.0; sites on affected versions should update now. Disclosed April 2021.
Vulnerability Overview
The Alkubot – Gamify discounts, sell more and give less at the right time plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.3.3. This is due to missing or incorrect nonce validation on the successfulBargain() function. This makes it possible for unauthenticated attackers to place arbitrary products in a shopping cart via a forged request granted they can trick a user into performing an action such as clicking on a link.
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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity.
CWE-352: Cross-Site Request Forgery (CSRF)
Alkubot < 3.0.0 carries this weakness at successfulBargain(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Alkubot the fix is 3.0.0: builds < 3.0.0 are affected, anything from 3.0.0 onward is not.
Remediation
Update to version 3.0.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Alkubot: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Alkubot 3.0.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C