Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-112293 Overview
CVE-2026-112293 is a missing authorization vulnerability [CWE-862] in the BoxyHQ Enterprise SaaS Starter Kit through version 1.6.0. The payment API routes under /pages/api/teams/[slug]/payments/ skip the team_payments permission check defined in lib/permissions.ts. Authenticated team members with the MEMBER or ADMIN role can invoke billing endpoints that should be restricted to team owners. Affected endpoints include create-portal-link, create-checkout-session, and products. Successful exploitation lets non-owner users open Stripe billing portals, view invoices, change payment methods, and alter subscriptions for the team.
Critical Impact
Non-owner team members can access Stripe billing portals, view invoices, and modify subscription and payment data for their team.
Affected Products
- BoxyHQ Enterprise SaaS Starter Kit versions through 1.6.0
- Deployments using the payments API routes with Stripe billing enabled
- Multi-tenant SaaS applications derived from the vulnerable starter kit
Discovery Timeline
- 2026-10-19 - CVE-2026-112293 published to the National Vulnerability Database
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-112293
Vulnerability Analysis
The BoxyHQ SaaS Starter Kit implements role-based access control through a permissions.ts module that maps resources to allowed roles. The team_payments resource is intended to restrict billing operations to users with the OWNER role. The payment API handlers under pages/api/teams/[slug]/payments/ authenticate the session but fail to call the permission check against team_payments. Any authenticated member of a team can therefore execute billing operations.
Exploitation requires only a valid session and membership in the target team. An attacker uses existing low-privilege credentials to issue requests against the affected API routes. The impact extends to confidentiality of invoice data and integrity of subscription configuration.
Root Cause
The root cause is a missing authorization check in three API route handlers: create-checkout-session.ts, create-portal-link.ts, and products.ts. These handlers verify session authentication and team membership but do not invoke the throwIfNoTeamAccess or equivalent permission guard tied to the team_payments resource. The permissions model defined in lib/permissions.ts is never enforced on this code path.
Attack Vector
The attack is executed over the network against the application's HTTP API. An authenticated MEMBER or ADMIN of a team sends a request to /api/teams/{slug}/payments/create-portal-link to receive a signed Stripe Customer Portal URL. Loading that URL grants access to invoices, payment methods, and subscription controls that belong to the team owner. The same technique applies to create-checkout-session and products, enabling subscription changes without owner consent.
For technical details, review the GitHub Permissions Code File, the GitHub Create Portal Link API handler, and the VulnCheck Security Advisory.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-112293
Indicators of Compromise
- Access log entries showing requests to /api/teams/{slug}/payments/create-portal-link, /create-checkout-session, or /products from users whose team role is not OWNER.
- Unexpected redirects to billing.stripe.com Customer Portal sessions initiated by non-owner accounts.
- Stripe audit events showing subscription or payment-method changes correlated with sessions tied to MEMBER or ADMIN users.
Detection Strategies
- Correlate web server access logs with the application's role database to flag payment route calls by non-owner principals.
- Enable Stripe's audit log forwarding and alert on customer.subscription.updated, payment_method.attached, and billing_portal.session.created events outside expected owner workflows.
- Add server-side instrumentation around the payment handlers that logs the authenticated user role and emits a security event when the role is not OWNER.
Monitoring Recommendations
- Ingest application and reverse-proxy access logs into a centralized analytics platform and build detections keyed on the three affected route paths.
- Monitor Stripe webhook traffic for subscription modifications and compare the initiating user against the authoritative team-owner record.
- Track anomalous session activity for team accounts, including portal link generation outside business hours or from new source addresses.
How to Mitigate CVE-2026-112293
Immediate Actions Required
- Audit all teams for recent payment route activity and reconcile Stripe subscription and payment-method state against expected owner-driven changes.
- Temporarily disable or gate the /api/teams/[slug]/payments/* routes at the reverse proxy until an authorization fix is deployed.
- Rotate Stripe API keys and invalidate active Customer Portal sessions if evidence of misuse is found.
Patch Information
At the time of publication, the upstream repository tracks the issue in GitHub Issue #2511. Operators should monitor the BoxyHQ repository for a release that adds the team_payments permission check to the three affected handlers and upgrade once published. Review the VulnCheck Security Advisory for remediation status.
Workarounds
- Patch forks locally by invoking the existing throwIfNoTeamAccess or equivalent team_payments permission guard at the top of create-checkout-session.ts, create-portal-link.ts, and products.ts.
- Enforce authorization at the API gateway or middleware layer by rejecting requests to /payments/* routes when the caller's role is not OWNER.
- Restrict Stripe Customer Portal configuration to disable self-service subscription and payment-method changes until the application-level fix is in place.
# Example reverse-proxy guard (NGINX) blocking non-owner access until patched
location ~ ^/api/teams/[^/]+/payments/(create-portal-link|create-checkout-session|products)$ {
if ($http_x_team_role != "OWNER") {
return 403;
}
proxy_pass http://app_upstream;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

