# BUG: Billing vulnerability - quota reset and renewal charge are not synchronized

**URL:** <https://forum.cursor.com/t/bug-billing-vulnerability-quota-reset-and-renewal-charge-are-not-synchronized/177725>\
**Category:** Bug Reports\
**Created:** [November 8, 2026, 12:52pm UTC](https://forum.cursor.com/t/bug-billing-vulnerability-quota-reset-and-renewal-charge-are-not-synchronized/177725 "2026-11-08T12:52:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![TCCC](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tccc/32/125125_2.png) [@TCCC](https://forum.cursor.com/u/TCCC)\
**Post date:** [November 8, 2026, 12:52pm UTC](https://forum.cursor.com/t/bug-billing-vulnerability-quota-reset-and-renewal-charge-are-not-synchronized/177725/1 "2026-11-08T12:52:56Z")

</div>

### Describe the Bug

Billing logic flaw: when a paid subscription (Pro / Pro+ / Ultra) reaches its renewal time, the new billing cycle’s usage quota is reset immediately, but the renewal charge/invoice is only issued about 1 hour later. Quota is granted before payment is confirmed.

During this ~1 hour window, the account can consume the full quota of the new cycle without having paid for it. If the invoice is then left unpaid (unpaid/“red” invoice), the consumed usage is never paid for.

This is being actively abused: “near-expiry” / “quota-burn” Cursor accounts are sold on gray markets specifically so buyers can burn the next cycle’s quota for free in this window. This causes direct revenue loss and is unfair to paying users.

### Steps to Reproduce

1. Use an account with an active paid subscription (Pro, Pro+ or Ultra) whose current period ends at a known time (e.g. Nov 8, 12:00).
2. Ensure the payment method will not succeed for the renewal (e.g. card removed / insufficient balance / card canceled).
3. At the exact renewal minute, open Settings → Usage: the usage quota has already been reset to the full amount for the new cycle.
4. Note that no charge has been made and no invoice has been issued yet.
5. Immediately consume usage heavily (e.g. multiple parallel Agent sessions with premium models).
6. About 1 hour later, the renewal invoice is generated and shows as unpaid.
7. Observe that all usage consumed between the renewal minute and invoice generation was served without payment, and is not clawed back.

### Operating System

Windows 10/11

### Version Information

Menu → About Cursor → Copy

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![TCCC](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tccc/32/125125_2.png) [@TCCC](https://forum.cursor.com/u/TCCC)\
**Post date:** [November 8, 2026, 12:59pm UTC](https://forum.cursor.com/t/bug-billing-vulnerability-quota-reset-and-renewal-charge-are-not-synchronized/177725/4 "2026-11-08T12:59:55Z")

</div>

@Colin Could you please look into this billing vulnerability? Near-expiry Cursor accounts are being openly resold on the black market to exploit it, and this has been going on for quite a while. It’s unfair to paying users — hoping the team can address it soon. Thanks!