CVE-2026-12501

WP Travel Engine < 6.8.2 - Unauthenticated Payment Bypass via Missing PayPal IPN Receiver and Amount Verification

Published Aug 6, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
The WP Travel Engine WordPress plugin before 6.8.2 does not verify that an incoming PayPal payment notification was sent to the site's configured merchant account, nor that the paid amount matches the order total, before marking a booking as paid, allowing unauthenticated attackers to mark bookings as fully paid using a token payment made to an attacker-controlled account.

Analysis

AI-generated

Technical impact

The WP Travel Engine plugin suffers from a CWE‑345 weakness: it does not verify that an incoming PayPal payment notification originated from the site’s merchant account, nor does it confirm that the notified amount matches the order total. As a result, an attacker can send a crafted notification and cause a booking to be marked as fully paid without having actually paid. This flaw allows unauthenticated users to manipulate payment status, potentially causing revenue loss and opening the door for fraudulent overbooking.

Affected Systems

WordPress sites using the WP Travel Engine plugin prior to version 6.8.2 are affected. The issue applies to all installations that rely on PayPal IPN for payment confirmation without additional verification steps.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity. An EPSS score of < 1% indicates a very low probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog, suggesting limited documented exploitation. Attackers can exploit this remotely by sending a forged IPN request directly to the site’s PayPal notification endpoint, so authentication is not required. The required conditions are that the site accepts IPN callbacks and the attacker can control the PayPal account used to send the notification.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade WP Travel Engine to version 6.8.2 or later.
  • Disable the PayPal payment method until a patched version is deployed, or block the IPN endpoint from unknown sources.
  • Configure the plugin to validate that IPNs come from the site’s own merchant account and that the amount matches the original order total.

Generated by OpenCVE AI on August 7, 2026 at 18:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions wp Travel Engine
Vendors & Products Wordpress-extensions
Wordpress-extensions wp Travel Engine
Type Values Removed Values Added
Weaknesses CWE-20
CWE-285
Type Values Removed Values Added
Weaknesses CWE-345
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-20
CWE-285
Type Values Removed Values Added
Description The WP Travel Engine WordPress plugin before 6.8.2 does not verify that an incoming PayPal payment notification was sent to the site's configured merchant account, nor that the paid amount matches the order total, before marking a booking as paid, allowing unauthenticated attackers to mark bookings as fully paid using a token payment made to an attacker-controlled account.
Title WP Travel Engine < 6.8.2 - Unauthenticated Payment Bypass via Missing PayPal IPN Receiver and Amount Verification
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Aug 7, 2026, 2:08 PM
Reserved
Jun 17, 2026, 9:10 AM
Status
Deferred
Published
Aug 6, 2026, 10:16 PM
Modified
Aug 26, 2026, 4:31 PM