CVE-2026-87974

Asaas Gateway for WooCommerce < 2.7.8 - Unauthenticated Arbitrary Order Status Manipulation

2026-10-14 00:00

Strategic Overview

Status: Patched in 2.7.8
Affected Plugin: Asaas Gateway for WooCommerce
Affected Version: < 2.7.8
CVSS: 5.3Medium
Weakness type: CWE-345 · Insufficient Verification of Data Authenticity
CVE: CVE-2026-87974

View all Asaas Gateway for WooCommerce vulnerabilities

At a glance

CVE-2026-87974 is a medium-severity Insufficient Verification of Data Authenticity vulnerability in the Asaas Gateway for WooCommerce WordPress plugin, affecting versions < 2.7.8. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.7.8; sites on affected versions should update now. Disclosed October 2026, reported by Guillermo Álvarez Fernández.

Vulnerability Overview

The Asaas Gateway for WooCommerce plugin for WordPress is vulnerable to Authentication Bypass in all versions up to 2.7.8. This is due to missing enforcement of a non-empty access token in the webhook token validator (an empty configured token matched any empty request token) and the absence of server-side verification that the Asaas-confirmed payment corresponds to the order being completed. This makes it possible for unauthenticated attackers to mark arbitrary WooCommerce orders as paid without authentication, by sending a webhook request with an empty access token and a payment ID that does not correspond to the targeted order.

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.

CWE-345: Insufficient Verification of Data Authenticity

The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

Remediation

Update to version 2.7.8, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Asaas Gateway for WooCommerce 2.7.8 closes this, and updating the plugin is the step that ends it.

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-87974 https://www.wordfence.com/threat-intel/vulnerabilities/id/56a070d9-64bb-49d3-bb8f-071719ae8d10 https://nvd.nist.gov/vuln/detail/CVE-2026-87974

CVSS Vector

5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/