Skip to main content

Quick Paypal Payments EUVDEUVD-2026-57176

| CVE-2026-17008 MEDIUM
2026-08-12 WPScan GHSA-wpmj-p56j-6mq2
5.3
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Initiate checkout as any buyer
  2. Delivery
    Obtain valid order token from plugin
  3. Exploit
    Submit trivial PayPal payment against order
  4. Install
    IPN callback received by plugin
  5. C2
    Plugin matches token, skips amount and status checks
  6. Execute
    Order marked fully paid
  7. Impact
    Goods or services obtained without full payment

Vulnerability Assessment

Exploitation Conditions

The target site must be running the Quick Paypal Payments WordPress plugin at version 5.7.50 or earlier with an active PayPal IPN endpoint configured and receiving callbacks. An attacker must be able to initiate a standard checkout to obtain a valid order token - this requires no special privileges beyond being a store customer. Exploitation further requires the attacker to trigger a PayPal IPN callback to the vulnerable endpoint, either by completing a real low-value PayPal payment or by crafting a forged IPN request if the plugin does not independently verify payload authenticity with PayPal's verification API. Exploitation is bounded to WordPress sites actively using this specific plugin for payment processing; sites using any other payment gateway are unaffected. The CVSS vector PR:N is consistent with the buyer-level access required, as no administrative or authenticated session is needed beyond normal checkout initiation.

Impact

The NVD CVSS score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) substantially understates the real-world business impact: this is a direct financial fraud enabler, not merely an abstract integrity flaw. The zero-complexity exploitation path - initiate checkout, pay a trivial amount, receive goods - combined with publicly available exploit code from WPScan means the effective attacker skill threshold is negligible. No EPSS score was provided in available data, and the vulnerability is not currently listed in CISA KEV, suggesting widespread automated exploitation has not yet been confirmed; however, the simplicity and financial upside of this attack make sustained attacker interest likely. Even a mid-sized municipal IT team in boleslawiec operating a WordPress-based e-commerce storefront should treat this as urgent given that any customer-facing checkout flow is a direct attack surface. The SSVC signals reinforce urgency: the attack is automatable (no manual interaction required beyond initiating a checkout), the technical impact is direct financial loss to merchants, and no patch is currently available. The 'Information Disclosure' tag present in the intelligence metadata appears mislabeled and should not inform risk prioritization - the actual harm is business logic bypass enabling payment fraud.

Exploit ScenarioDerived

A buyer initiates a legitimate checkout on a WordPress site running Quick Paypal Payments, obtains a valid order token through the standard purchase flow, and submits a PayPal payment of a negligible amount such as $0.01 against a full-price order. The plugin's IPN handler receives the PayPal callback, matches the order token, and immediately marks the order as fully paid without inspecting the amount, receiver, or status fields. A publicly available exploit from WPScan documents this technique, meaning systematic and automated fraud across multiple storefronts is realistic for a motivated attacker.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 12, 2026

Fraudulent order completion in the Quick Paypal Payments WordPress plugin (all versions through 5.7.50) enables any buyer to acquire full-price goods or services by paying an arbitrary small amount. The plugin's PayPal IPN handler validates only the order token when determining whether to mark an order as paid - ignoring the payment amount, receiver address, and payment status entirely - so any buyer who can initiate a checkout can trivially complete a full-value order for pennies. Publicly available exploit code exists, reported by WPScan, making immediate opportunistic exploitation straightforward for any motivated attacker targeting affected WordPress storefronts.

RemediationAI

No vendor-released patch has been identified at time of analysis for any version of Quick Paypal Payments. Site administrators should immediately deactivate and remove the plugin from all WordPress installations to eliminate the attack surface; leaving it active while awaiting a patch is not advisable given the publicly available exploit. As an urgent compensating measure, merchants should cross-reference all recent orders processed through this plugin against their PayPal transaction history to identify discrepancies between order totals and actual payment amounts received - any mismatch indicates potential fraud. Enabling PayPal's transaction dispute alerts and seller notification emails can surface future fraud attempts during any interim period. Replacing the plugin with a well-maintained, actively audited PayPal integration - such as the official WooCommerce PayPal Payments plugin - is strongly recommended as a permanent solution. Refer to the WPScan advisory at https://wpscan.com/vulnerability/605c0c65-6258-411a-a028-f3de25613bdf/ for ongoing patch status updates.

Affected VersionsENISA

Quick Paypal Payments 0 ≤5.7.50

Affected Packages

euvd quick_paypal_payments no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

PayPal's Instant Payment Notification (IPN) system delivers asynchronous HTTP callbacks to a merchant-configured endpoint when payment events occur. A correctly implemented IPN handler must validate at minimum: that the payment_status field equals 'Completed', that the mc_gross amount matches the expected order total, and that the receiver_email corresponds to the merchant's PayPal account - and optionally verify the payload authenticity with PayPal's IPN verification API. The Quick Paypal Payments plugin (CPE: cpe:2.3:a:unknown:quick_paypal_payments:*:*:*:*:*:*:*:*) skips all of these checks and relies solely on an order-token match to approve an order, constituting a business logic failure. No CWE is formally assigned, but the flaw most closely maps to CWE-345 (Insufficient Verification of Data Authenticity) and CWE-602 (Client-Side Enforcement of Server-Side Security). The CPE vendor field is listed as 'unknown' in NVD, indicating the publisher identity was not resolved at ingestion time, though the plugin identity is otherwise unambiguous.

Know when Quick Paypal Payments gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
vuln.today AI 5.3 MEDIUM

Network-accessible IPN endpoint requires no authentication beyond buyer checkout initiation; integrity impact is scoped to fraudulent order status; no confidentiality or availability impact is introduced.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

DescriptionCVE.org

The Quick Paypal Payments WordPress plugin through 5.7.50 does not verify the paid amount, receiver, or payment status in its PayPal IPN handler and marks an order paid on an order-token match alone, so a buyer who pays an arbitrary small amount can have a full-price order marked paid.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
Low
niche WordPress payment plugin, limited e-commerce market share
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy