Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain valid order transaction id
-
DeliveryCraft forged unsigned PayPal webhook
-
ExploitPOST to plugin notification endpoint
-
ExecutionPlugin skips signature verification
-
ImpactFraudulent payment confirmed or subscription cancelled
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Anti-spoofing controls
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the Premium Packages plugin (versions 7.0.0 up to but not including 7.2.1) to be installed and configured to process PayPal payments/subscriptions via webhooks/IPN, and the attacker must know a valid PayPal transaction id for an existing order on the site (obtainable from receipts, confirmation emails, exports, or logs). No authentication and no user interaction are needed (PR:N/UI:N) - the forged notification is delivered directly to the plugin's unauthenticated webhook handler, which processes it because it never validates PayPal's signature. Limiting factors: the transaction-id prerequisite makes attacks targeted rather than blind/mass, and impact is confined to payment/subscription state integrity (no data disclosure or availability loss). |
| Impact | Moderate-but-narrow risk. The NVD CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N = 5.3) is internally consistent with the description: a network-reachable, unauthenticated webhook endpoint (PayPal IPN/webhook) that fails to verify the cryptographic signature (CWE-290, authentication bypass by spoofing). Impact is correctly scoped to integrity only (I:L) - an attacker can forge a payment 'completed' event (fraudulently unlocking a paid package/subscription) or forge a subscription-cancellation event (denying a legitimate user their access), but cannot read data (C:N) or take down the service (A:N). The one real limiter, understated by AC:L, is that the attacker must know the target order's PayPal transaction id; these are not high-entropy secrets (they appear in receipts, confirmation emails, exports and logs) so AC:L is defensible, though it keeps exploitation targeted rather than fully mass-automatable. No EPSS score, no CISA KEV listing, and no public POC are present in the provided intelligence - so this is a legitimate but low-urgency financial-integrity bug, not an emergency: prioritize for revenue/payment-integrity reasons on sites actually running this plugin, but it is not a widespread-exploitation threat. Exploitation status: no public exploit identified at time of analysis. |
| Exploit ScenarioDerived | An attacker obtains a valid PayPal transaction id for an order on a target site (from a leaked receipt, email, log, or their own past order) and sends a forged, unsigned PayPal webhook to the plugin's notification endpoint claiming that payment for that order completed - the plugin accepts it without verifying PayPal's signature and grants the associated premium package/subscription for free. The same flaw lets the attacker POST a forged subscription-cancellation event to revoke a legitimate customer's active subscription. No public POC or active exploitation is reported at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
Unauthenticated attackers can forge PayPal payment and subscription-cancellation notifications against WordPress sites running the Premium Packages plugin before 7.2.1, because the plugin processes webhook/IPN payloads without verifying PayPal's signature. The transaction-id prerequisite makes attacks targeted rather than blind, and the impact is limited to payment and subscription state integrity (CVSS 5.3, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) with no data disclosure or availability loss. A vendor patch is available in 7.2.1; no public exploit code or confirmed active exploitation was identified at time of analysis.
RemediationAI
Upgrade the Premium Packages WordPress plugin to version 7.2.1 or later - the vendor has released a patch, and this is the only complete fix because it restores PayPal signature verification in the notification handler; advisory detail is at https://wpscan.com/vulnerability/edc2f15c-a72b-47c2-ad38-e6f5a8441d72/. If upgrading immediately is not possible, the most effective compensating control is to temporarily disable PayPal webhook/IPN-based payment and subscription processing in the plugin and reconcile orders manually through the PayPal dashboard, accepting the trade-off that automated payment confirmation and subscription lifecycle management will stop and customers may see delayed fulfilment. As a partial measure, restrict the plugin's notification endpoint at the web server or WAF so that only PayPal's published source IP ranges can reach it and reject requests carrying unexpected content types - this reduces opportunistic abuse but does not stop an attacker who can spoof or relay from an allowed origin, since the underlying signature check is still absent. Also reduce the exposure of PayPal transaction ids by scrubbing them from publicly accessible order exports, logs, and customer-facing emails where feasible, and audit existing orders and subscription records for forged confirmations or unexpected cancellations while the unpatched version remains in place.
Affected VersionsENISA
Affected Packages
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
The root cause is CWE-290 (Authentication Bypass by Spoofing): the Premium Packages plugin implements a PayPal notification handler (webhook/IPN endpoint) that accepts incoming payment and subscription events but does not validate PayPal's cryptographic signature before acting on them. Because the endpoint is reachable without authentication (PR:N) and requires no victim interaction (UI:N), any remote party who knows a valid PayPal transaction id for an existing order on the target site can craft a notification that the plugin treats as legitimate - confirming a payment that was never made or cancelling a subscription that should remain active. Transaction ids are typically obtainable from receipts, confirmation emails, store exports, or application logs, which is why the assessed attack conditions require that knowledge rather than allowing mass blind forgery. The EUVD record places the practical affected range at Premium Packages 7.0.0 up to but not including 7.2.1; no CPE strings were supplied for this entry, so product identification rests on the WordPress plugin slug and the WPScan advisory. The assessed impact is confined to integrity (I:L) of payment/subscription records, with no confidentiality or availability component, and the vector aligns with the independent assessment.
Know when PHP 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
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Network-reachable unauthenticated webhook with no signature check (AV:N/PR:N/UI:N); transaction-id is low-entropy and obtainable so AC:L holds; integrity-only impact (forged payment/cancellation), no confidentiality or availability.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
4DescriptionCVE.org
The Premium Packages WordPress plugin before 7.2.1 does not verify PayPal's webhook signature before processing payment and subscription notifications, allowing unauthenticated attackers to forge payment confirmations and subscription-cancellation events against any order whose transaction id they know.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
EUVD-2026-85063
GHSA-wv8r-wv6j-wh9g
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB