Skip to main content
VulnerabilityPublished Updated

CVE-2026-30231: FlintSH Flare · Insecure Direct Object Reference

Affects FlintSH FlareSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.0 Medium : upgrade to 1.7.2 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.7.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Flare and flintsh/Flare to 1.7.2.

Affected software

ProductAffectedFixed in
FlintSHFlareAffected
  • <1.7.2
Fixed in
  • 1.7.2
GitHubflintsh/Flarepkg:github/flintsh/FlareOther threatsAffected
  • <1.7.2
Fixed in
  • 1.7.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade all Flare instances to version 1.7.2 or later immediately to apply the official patch that enforces proper authorization on direct file routes.
  2. Conduct a thorough audit of access control mechanisms across all endpoints, especially those exposing direct resource URLs, to ensure consistent enforcement of ownership and permission checks.
  3. Implement strict authentication and session management policies to reduce the risk of credential compromise, as the vulnerability requires authenticated access.
  4. Monitor access logs for unusual file retrieval patterns by authenticated users to detect potential exploitation attempts.
  5. Consider implementing additional application-layer controls such as rate limiting and anomaly detection on file access endpoints.
  6. Educate users about the importance of safeguarding credentials and report suspicious activity promptly.
  7. If upgrading immediately is not feasible, restrict access to the Flare platform to trusted networks or VPNs to limit exposure.
  8. Review and enhance logging and alerting capabilities to capture unauthorized access attempts for forensic analysis.
  9. Evaluate the sensitivity of files stored and shared via Flare and apply encryption or additional protections where appropriate.
  10. Engage in regular vulnerability assessments and penetration testing to identify similar authorization weaknesses proactively.

Description

Flare is a Next.js-based, self-hostable file sharing platform that integrates with screenshot tools. Prior to version 1.7.2, the raw and direct file routes only block unauthenticated users from accessing private files. Any authenticated, non‑owner user who knows the file URL can retrieve the content, which is inconsistent with stricter checks used by other endpoints. This issue has been patched in version 1.7.2.

References

Community reviews

Loading reviews…