CVE-2026-88998

Tickera – Sell Tickets & Manage Events < 3.6.0.4 - Unauthenticated Arbitrary Order Payment Confirmation

2026-10-14 00:00
Ryan Fabella

Strategic Overview

Status
Patched in 3.6.0.4
Affected Version
< 3.6.0.4
CVSS
5.3Medium
Weakness type
CWE-345 · Insufficient Verification of Data Authenticity
CVE
CVE-2026-88998
View all Tickera – Sell Tickets & Manage Events vulnerabilities

At a glance

CVE-2026-88998 is a medium-severity Insufficient Verification of Data Authenticity vulnerability in the Tickera WordPress plugin, affecting versions < 3.6.0.4. 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 3.6.0.4; sites on affected versions should update now. Disclosed October 2026, reported by Ryan Fabella.

Vulnerability Overview

The Tickera – Sell Tickets & Manage Events plugin for WordPress is vulnerable to Payment Verification Bypass in all versions up to 3.6.0.4. This is due to an incorrect option key in the payment notification hash computation — `get_option( 'sid', 'secret_word', '2checkout' )` returned the SID instead of the secret word, meaning the HMAC signature never incorporated the secret credential and was trivially reproducible by any attacker who knew the SID. This makes it possible for unauthenticated attackers to mark arbitrary orders as paid without completing payment by forging a 2Checkout payment notification with a predictable hash signature. The 2Checkout payment gateway must be enabled and configured in the plugin settings.

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 3.6.0.4, 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: Tickera 3.6.0.4 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