Summary
CVE-2026-18031 is a critical improper authentication vulnerability (CWE-287) in the TabaPay Gateway WordPress plugin, versions through 1.4.0. The plugin fails to validate the payment callback before establishing a user session, allowing an unauthenticated remote attacker to log in as any registered user — including administrators. The flaw carries a CVSS v3.1 base score of 9.8 (Critical) and can lead to full site compromise.
Technical details
- Root cause: The plugin’s payment callback handler establishes a logged-in session for the user tied to the referenced order without first validating that the callback actually originated from TabaPay or that the requester is authorized to act on that order.
- Trigger conditions: An attacker sends a crafted, unauthenticated request to the plugin’s payment callback endpoint, referencing an arbitrary order/user.
- Attack vector: Network-based, no authentication or user interaction required, low attack complexity (AV:N/AC:L/PR:N/UI:N).
- Impact: Full authentication bypass — an attacker can impersonate any registered user, including site administrators, resulting in complete compromise of confidentiality, integrity, and availability of the WordPress site.
Affected software
- TabaPay Gateway WordPress plugin — versions 0 through 1.4.0 (all known releases up to and including 1.4.0)
Severity
- CVSS v3.1 Base Score: 9.8 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: As of this writing, no patched version of the TabaPay Gateway plugin has been identified. Security teams should monitor the plugin vendor and the WordPress.org plugin repository for a fixed release and apply it as soon as it becomes available.
- If no patch is available:
- Deactivate and remove the TabaPay Gateway plugin from production WordPress sites until a fix is released.
- Restrict or firewall access to the plugin’s payment callback endpoint at the network/WAF layer, allowing traffic only from TabaPay’s known IP ranges.
- Monitor authentication logs for anomalous admin/user logins that correlate with requests to the payment callback endpoint.
- Enforce multi-factor authentication for administrator accounts to limit the impact of a successful session hijack.
- Review recent order/payment activity and active sessions for signs of unauthorized administrative access.

