Grida through 0.0.24 Missing Authorization in Forms File-Preview API
Affects Grida 0.0.24 and earlier, including forms that use external Supabase storage. The checked facts list no fixed version.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Grida, a forms application, contains a missing authorization flaw in its Forms file-preview API that lets an unauthenticated attacker remotely read other organizations' form response files. The attacker can use public form and field IDs to obtain signed URLs for attachments and connected Supabase bucket objects.
Read the original description
Grida through 0.0.24 contains a missing authorization vulnerability in the Forms file-preview API routes that allows unauthenticated attackers to read other organizations' form response files. Attackers can use form and field IDs exposed in public form payloads with a chosen path parameter to obtain service-role signed URLs for attachments and connected Supabase bucket objects.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- gridaco grida
through 0.0.24
Evidence 7
- Patch
- Patch
- Report
- Repository
- Repository
Show all 7 sourcesShow fewer sources
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123623
Is CVE-2026-123623 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The form file-preview API does not check authorization. Requests without logging in can read files attached to other organizations' form responses, which may include respondents' personal data. For fields using external Supabase storage, the same path can read arbitrary files in the connected Supabase storage.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-123623?
grida: through 0.0.24.Source: cve.now feed data
Am I affected, and how do I check?
Grida version 0.0.24 and earlier is in the affected range. The external Supabase storage path applies only to forms with a field configured for external Supabase storage. To check a version, look at the grida version in the project's package.json or the installed package list.Source: vulncheck.com, github.com
How do I fix CVE-2026-123623?
The checked facts do not name a fixed version, so no upgrade target can be given from them. Check the Grida project's releases for a version later than 0.0.24 that addresses this advisory.Source: vulncheck.com, github.com