WebToffee released version 1.3.1 of its free Gift Cards for WooCommerce plugin on September 24, 2026, addressing a value-validation weakness. WPScan’s September 28 advisory identifies the finding as CVE-2026-91020; the CVE Program record was published separately on October 2. Those are different points in the remediation and disclosure sequence. [S01][S04][S05]
Value integrity and the distribution of a remedy
The WPScan-assigned CVE record says versions before 1.3.1 did not validate a customer-supplied gift-card amount on the server before using it for the cart price and store-credit value. It describes an unauthenticated amount-manipulation weakness capable of distorting the order total. This is a defect in reconciling authorised value with payment, rather than evidence that a legitimate recipient’s entire balance was stolen. [S04]
The affected identifier is wt-gift-cards-woocommerce. The free product issues digital gift-card codes, emails them to recipients and supports partial redemption with the remaining balance retained. WebToffee’s separately marketed premium product has its own version numbering; the reviewed advisory does not establish that it is affected. [S01][S02][S03]
The vendor’s complete changelog credits researcher Berke Bodur for the vulnerability fixed in 1.3.1, matching WPScan’s researcher attribution. Its next listed release, 1.3.2 on October 19, is described as a WooCommerce compatibility update. The September 24 release remains the dated security remedy in the reviewed record. [S01][S05]
WordPress.org’s daily series shows 22 downloads on September 23, 547 on the September 24 release date and 234 on September 25. The advisory date, September 28, records 78. These observations describe repository activity around the remedy; they do not identify the downloaded version or establish what caused a change in activity. [S06]
Daily repository downloads: WebToffee Gift Cards for WooCommerce
Official daily counts for September 14-October 4, 2026, spanning the security-remediation and disclosure period. Retrieved October 19.
downloads
Tap or hover for details. All values are also available in the data table.
Source
Repository activity, not unique stores, affected installations, gift-card sales or confirmed security updates. The response does not identify downloaded versions, successful installation or exploitation. Date labels are reproduced as returned; the API does not state a reporting timezone. No missing days are filled.
Show data tableHide data table
| Category | Repository-reported downloads |
|---|---|
| 2026-09-14 | 30 downloads |
| 2026-09-15 | 28 downloads |
| 2026-09-16 | 17 downloads |
| 2026-09-17 | 22 downloads |
| 2026-09-18 | 22 downloads |
| 2026-09-19 | 10 downloads |
| 2026-09-20 | 12 downloads |
| 2026-09-21 | 19 downloads |
| 2026-09-22 | 22 downloads |
| 2026-09-23 | 22 downloads |
| 2026-09-24 | 547 downloads |
| 2026-09-25 | 234 downloads |
| 2026-09-26 | 51 downloads |
| 2026-09-27 | 50 downloads |
| 2026-09-28 | 78 downloads |
| 2026-09-29 | 78 downloads |
| 2026-09-30 | 57 downloads |
| 2026-10-01 | 49 downloads |
| 2026-10-02 | 74 downloads |
| 2026-10-03 | 143 downloads |
| 2026-10-04 | 29 downloads |
The same installation can generate more than one repository interaction, and the returned daily series supplies no unique-store or completed-installation measure. The 547 figure must not be described as 547 merchants protected by the fix. It also says nothing about gift cards issued, unpaid orders or the number of successful attacks. [S06]
The current public WPScan page confirms the affected plugin, fix version, researcher and September 28 publication. The structured CVE record supplies the technical scope, while the vendor changelog independently establishes its release date. The reviewed records do not report observed exploitation, compromised-store counts or quantified merchant losses. [S01][S04][S05]
For a gift-card merchant, the material control is that a selected amount must match the value the store authorises and collects before creating spending credit. Public release and download records make the remedy’s availability visible, but leave the installed patch level and loss history of individual stores unresolved. [S04][S05][S06]