Skip to content

[GHSA-525j-95gf-766f] FileBrowser Quantum: Password-Protected Share Bypass via /public/api/share/info#8636

Open
ByteAfterlife wants to merge 1 commit into
ByteAfterlife/advisory-improvement-8636from
ByteAfterlife-GHSA-525j-95gf-766f
Open

[GHSA-525j-95gf-766f] FileBrowser Quantum: Password-Protected Share Bypass via /public/api/share/info#8636
ByteAfterlife wants to merge 1 commit into
ByteAfterlife/advisory-improvement-8636from
ByteAfterlife-GHSA-525j-95gf-766f

Conversation

@ByteAfterlife

@ByteAfterlife ByteAfterlife commented Jul 9, 2026

Copy link
Copy Markdown

Updates

  • CVSS v3
  • CVSS v4
  • Severity

Comments
In the original advisory (CVE-2026-27611) that this advisory extends on, it was marked as CVSS 3.1 being 6.5 by GitHub on the NVD (https://nvd.nist.gov/vuln/detail/CVE-2026-27611), this one received CVSS 7.5 (https://nvd.nist.gov/vuln/detail/CVE-2026-30933). When comparing the CVSS string of the original report with this one, the only difference is in this one, User Interaction is "none", but in the original one it is "required". I believe this difference is unfair because user interaction is still required in this advisory too because someone needs to make a share in the first place, just like the original advisory. I have changed the CVSS 3.1 to reflect the same one given to the original advisory.

@github

github commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

Hi there @gtsteffaniak! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.

This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

@github-actions github-actions Bot changed the base branch from main to ByteAfterlife/advisory-improvement-8636 July 9, 2026 20:03
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