Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-38rh-4v39-vfxv
No affected components available
Summary
The StripeYPT plugin includes a test.php debug endpoint that is accessible to any logged-in user, not just administrators. This endpoint processes Stripe webhook-style payloads and triggers subscription operations, including cancellation. Due to a bug in the retrieveSubscriptions() method that cancels subscriptions instead of merely retrieving them, any authenticated user can cancel arbitrary Stripe subscriptions by providing a subscription ID.
Details
At plugin/StripeYPT/test.php:4, the endpoint checks only for a logged-in user, not for admin privileges:
if (!User::isLogged())
At lines 27-29, the endpoint accepts a JSON payload from the request and processes it through the Stripe metadata handler:
$obj = StripeYPT::getMetadataOrFromSubscription(json_decode($_REQUEST['payload']));
The call chain proceeds as follows:
test.phpcallsgetMetadataOrFromSubscription()- Which calls
getSubscriptionId()to extract the subscription ID - Which calls
retrieveSubscriptions()to interact with the Stripe API
At StripeYPT.php:933, the retrieveSubscriptions() method contains a critical bug where it cancels the subscription instead of just retrieving it:
$response = $sub->cancel();
This same bug also affects the production webhook processing path via processSubscriptionIPN(), meaning both the debug endpoint and the live webhook handler can trigger unintended cancellations.
Proof of Concept
-
Log in as any regular (non-admin) user and obtain a session cookie.
-
Send a crafted payload to the test endpoint with a target subscription ID:
curl -b "PHPSESSID=USER_SESSION" \
"https://your-avideo-instance.com/plugin/StripeYPT/test.php" \
-d 'payload={"data":{"object":{"id":"sub_TARGET_SUBSCRIPTION_ID","customer":"cus_CUSTOMER_ID"}}}'
-
The endpoint processes the payload, calls
retrieveSubscriptions(), and the subscription is cancelled via the Stripe API. -
To enumerate subscription IDs, check if the application exposes them through other endpoints or use predictable patterns:
# Check user subscription details if accessible
curl -b "PHPSESSID=USER_SESSION" \
"https://your-avideo-instance.com/plugin/StripeYPT/listSubscriptions.php"
- The Stripe subscription is now cancelled. The affected user loses access to their paid features.
Impact
Any logged-in user can cancel arbitrary Stripe subscriptions belonging to other users. This causes direct financial damage to the platform operator (lost subscription revenue) and service disruption for paying subscribers who lose access to premium features. The debug endpoint should have been removed from production or restricted to admin-only access, and the retrieveSubscriptions() method should retrieve rather than cancel subscriptions.
- CWE-862: Missing Authorization
- Severity: Medium
Recommended Fix
Two changes are needed:
1. Restrict the debug endpoint to admins at plugin/StripeYPT/test.php:4:
// plugin/StripeYPT/test.php:4
if (!User::isAdmin())
Change User::isLogged() to User::isAdmin() so only administrators can access the debug endpoint.
2. Fix the retrieval bug at StripeYPT.php:933:
Remove the $sub->cancel() call from retrieveSubscriptions() so that the function only retrieves subscription data without cancelling it:
// StripeYPT.php:933 - remove the following line:
// $response = $sub->cancel();
The retrieveSubscriptions() method should retrieve subscription information, not cancel subscriptions as a side effect.
Found by aisafe.io
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the integrity of the data.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard