AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 30 Bitcoin

feat: add manual subscription date editing for admins (#7257)

Public commit record

What the developer wrote

Authored by Abhijay Jain

100/100 · Strong
feat: add manual subscription date editing for admins (#7257)

* feat: add manual subscription date editing for admins

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: Address code review feedback on subscription date editing

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: Use DateOnly params and normalize to UTC for date editing

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: added tests and API route

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: addressed coding suggestions

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: added null check

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* docs: updated swagger todocument manual subscription date editing

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* Slight adjustment

---------

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>
Co-authored-by: Nicolas Dorier <nicolas.dorier@gmail.com>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit adds a new admin-only feature that lets store administrators manually edit subscription start and expiration dates for subscribers, both through the web interface and the API. It is a normal feature addition, not a vulnerability fix. The code includes basic validation (expiration must be after start) and is restricted to users who already have permission to manage subscribers. There is no direct evidence in the commit that this introduces a security bug, but any date-editing feature could theoretically be misused by a compromised admin account or through authorization bugs.

Recommended action

No immediate action required; this is a feature commit. As a defensive review note, operators should ensure that API keys with `btcpay.store.canmanagesubscribers` scope are issued only to trusted parties, and audit logs of subscription date changes should be reviewed if available. If a security review is desired, focus on whether the `CanManageSubscribers` policy can be bypassed or overly granted.

Security signals we found

01

New privileged admin/API capability added (manual date override)

02

Authorization enforced by existing subscription management policy

03

Server-side date validation present (expiration after start)

04

Timezone offset bounds checked on UI controller (-840 to +840 minutes)

05

No input sanitization concerns beyond date/offset validation visible

06

No vendor disclosure of security relevance

Risk score

Why this scored 30/100

Our methodology →
Potential impact 5/30
Exploitability 5/25
Stealth signal 5/15
Affected reach 5/15
Confidence 7/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.