Skip to content

Fix author update authorization and recovery token validation - #417

Merged
svera merged 1 commit into
svera:developfrom
overskye:main
Oct 17, 2026
Merged

svera merged 1 commit into
svera:developfrom
overskye:main

Conversation

@overskye

Copy link
Copy Markdown
Contributor

Hi! Here are a couple of fixes 👀

Run the author update handler only after mandatory authentication and administrator checks, preventing anonymous and regular users from changing indexed author metadata

Reject unknown password recovery UUIDs before accessing the recovery expiry field, avoiding a nil-pointer panic on public reset-password requests

Add regression tests for anonymous, regular, and administrator access to author updates, and for reset-password requests with unknown recovery tokens

Run the author update handler only after mandatory authentication and administrator checks, preventing anonymous and regular users from changing indexed author metadata.

Reject unknown password recovery UUIDs before accessing the recovery expiry field, avoiding a nil-pointer panic on public reset-password requests.

Add regression tests for anonymous, regular, and administrator access to author updates, and for reset-password requests with unknown recovery tokens.
@svera
svera changed the base branch from main to develop October 17, 2026 07:31

@svera svera left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the PR @overskye , approved!

@svera
svera merged commit 8574914 into svera:develop Oct 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants