PT-2026-37299 · Packagist · Wwbn Avideo

Published

2026-05-05

·

Updated

2026-05-05

·

CVE-2026-43883

CVSS v3.1

4.2

Medium

VectorAV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L

Summary

plugin/PayPalYPT/agreementCancel.json.php cancels a PayPal billing agreement using an attacker-supplied agreement parameter without verifying that the authenticated user owns the agreement. A low-privilege authenticated user who learns or obtains another user's PayPal billing agreement ID can silently suspend the victim's recurring subscription, causing revenue loss to the platform and loss of paid service to the victim.

Details

AVideo's PayPalYPT plugin ships two near-duplicate endpoints that cancel a PayPal billing agreement. Only one of them enforces ownership:
  • plugin/PayPalYPT/PayPalAgreementCancel.json.php:19 — correctly requires either admin or the agreement's owner:
if (!User::isAdmin() && !Subscription::isAgreementFromUser($ POST['agreement id'], User::getId())) {
  $obj->msg = "Only the owner can delete his agreement";
  die(json encode($obj));
}
  • plugin/PayPalYPT/agreementCancel.json.php:9-26 — only checks User::isLogged() (in fact twice, redundantly) and then calls the cancellation directly:
if (!User::isLogged()) { ... die; }       // line 9
if (empty($ REQUEST['agreement'])) { ... die; }  // line 14
if (!User::isLogged()) { ... die; }       // line 19 — duplicate; no ownership check
$plugin = AVideoPlugin::loadPluginIfEnabled("PayPalYPT");
$agreement = PayPalYPT::cancelAgreement($ REQUEST['agreement']); // line 26
PayPalYPT::cancelAgreement() at plugin/PayPalYPT/PayPalYPT.php:548-566 resolves the agreement ID against PayPal and calls $createdAgreement->suspend($agreementStateDescriptor, $apiContext) unconditionally — the server does not verify that the logged-in user's users id matches the owner recorded in PayPalYPT log (or wherever the agreement was registered):
public static function cancelAgreement($agreement id)
{
  ...
  $createdAgreement = self::getBillingAgreement($agreement id);
  try {
    $createdAgreement->suspend($agreementStateDescriptor, $apiContext);
    return Agreement::get($createdAgreement->getId(), $apiContext);
  } catch (Exception $ex) {
    return false;
  }
}
The intended UI caller is subscriptions list.php:84 which posts the current user's own agreement IDs — but the server accepts any agreement parameter from any logged-in user. Agreement IDs can leak via error log entries written in agreementCancel.json.php:34 and webhook.php during normal operation, via PayPal receipt emails, or via other administrative and payment-log screens. No CSRF token is required, but the root defect is missing authorization, not CSRF.

PoC

  1. Log in as any low-privilege user (registered subscriber, commenter, free-tier account created via signUp).
  2. Obtain the target's PayPal agreement ID (e.g., I-ABCD1234XYZ). This may come from server error logs, email receipts, admin/payment screens, or other disclosures.
  3. Send the request with the victim's agreement ID:
curl -X POST 'https://target.example/plugin/PayPalYPT/agreementCancel.json.php' 
 -b 'PHPSESSID=<attacker session>' 
 -d 'agreement=I-ABCD1234XYZ'
  1. Expected response:
{"error":false,"msg":""}
The victim's billing agreement is suspended at PayPal via Agreement::suspend() (PayPalYPT.php:560). The victim stops being billed; AVideo subsequently reflects the subscription as inactive.

Impact

  • Any authenticated user can silently cancel another user's active PayPal recurring billing agreement.
  • Revenue disruption for the platform operator — any affected subscribers stop being billed.
  • Service disruption for the victim — their paid subscription lapses.
  • The defect is purely an authorization gap; the sister endpoint PayPalAgreementCancel.json.php demonstrates that the owner/admin check was intentional for this action but was not applied to this duplicate.

Recommended Fix

Port the ownership check from the sister endpoint into agreementCancel.json.php:
if (!User::isAdmin() && !Subscription::isAgreementFromUser($ REQUEST['agreement'], User::getId())) {
  $obj->msg = "Only the owner can cancel this agreement";
  die(json encode($obj));
}
Alternative, preferred remediation: delete the duplicate agreementCancel.json.php entirely and point the cancelAgreement() JS helper in subscriptions list.php:84 at the already-protected PayPalAgreementCancel.json.php endpoint (sending the expected agreement id POST field). While patching, also remove the redundant second User::isLogged() branch at line 19.

Fix

IDOR

Weakness Enumeration

CWE-639

Related Identifiers

CVE-2026-43883
GHSA-958H-QP3X-Q4GJ

Affected Products

Wwbn Avideo