MEDIUM 6.5

CVE-2026-14792: Formbricks 5.0.0 Improper Access Control Vulnerability (CVSS 6.5)

A security flaw in Formbricks 5.0.0 allows remote attackers to bypass access controls on survey-related functionality without requiring authentication. The vulnerability exists in the survey link handling component and can be exploited to modify data or disrupt availability. Upgrading to version 5.1.0-rc.1 or later resolves the issue.

Source data · NVD / CISA · public domain

CVSS
3.1 · 6.5 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Weaknesses (CWE)
CWE-266, CWE-284
Affected products
0 configuration(s)
Published / Modified
2026-07-06 / 2026-07-07

NVD description (verbatim)

A security vulnerability has been detected in Formbricks 5.0.0. This impacts an unknown function of the file apps/web/modules/survey/link/actions.ts of the component Survey Handler. The manipulation leads to improper access controls. Remote exploitation of the attack is possible. Upgrading to version 5.1.0-rc.1 will fix this issue. The identifier of the patch is af6023b5ac3b030ffcea24fac799f76f3e3512c6. You should upgrade the affected component.

8 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-14792 is a medium-severity improper access control vulnerability (CVSS 3.1 score 6.5) affecting the Survey Handler component in Formbricks. The flaw resides in apps/web/modules/survey/link/actions.ts and stems from insufficient authorization checks, as indicated by the CWE-266 (Improper Privilege Management) and CWE-284 (Improper Access Control By User in User Interface) classifications. The vulnerability is remotely exploitable without authentication or user interaction, operating on the network attack surface with low attack complexity.

Business impact

Organizations deploying Formbricks 5.0.0 for survey distribution and data collection face integrity and availability risks. An attacker could modify survey responses, alter survey logic, or degrade service availability. For enterprises relying on Formbricks for customer feedback, market research, or internal assessments, this could compromise data accuracy and customer trust. The lack of authentication requirement increases the attack surface significantly—any network-exposed instance is potentially at risk.

Affected systems

Formbricks 5.0.0 is confirmed vulnerable. Version 5.1.0-rc.1 and later contain the fix (commit af6023b5ac3b030ffcea24fac799f76f3e3512c6). Organizations using version 5.0.0 should assume they are affected if the survey link handler is exposed to untrusted networks. Verify your deployment version and check whether apps/web/modules/survey/link/actions.ts has been updated.

Exploitability

This vulnerability is exploitable remotely without authentication, user interaction, or special privileges. An attacker only needs network connectivity to the affected Formbricks instance. The low attack complexity means no special techniques or conditions are required to trigger the flaw. However, this vulnerability is not currently tracked in the CISA Known Exploited Vulnerabilities (KEV) catalog, suggesting active exploitation has not yet been widely documented. Organizations should not rely on absence from KEV as grounds for deferring remediation.

Remediation

Immediately upgrade Formbricks to version 5.1.0-rc.1 or later. If a stable (non-RC) release is available beyond 5.1.0-rc.1, prioritize that. Apply the patch containing commit af6023b5ac3b030ffcea24fac799f76f3e3512c6. As an interim mitigation, restrict network access to the Formbricks instance via firewall or reverse proxy to limit exposure to trusted users and IP ranges. However, this is not a substitute for patching.

Patch guidance

The fix is available in version 5.1.0-rc.1 and later. Consult the official Formbricks release notes and repository to confirm the stable release schedule. If only an RC version is available in your environment, evaluate the stability and maturity of that RC release before deploying to production. Given the MEDIUM severity and remote exploitability, patch deployment should be prioritized within your standard change management window—typically within 2–4 weeks, but sooner if the instance is internet-facing. Test the upgrade in a staging environment to confirm survey functionality and existing data integrity.

Detection guidance

Monitor access logs to apps/web/modules/survey/link/actions.ts for unauthorized or anomalous requests. Look for patterns indicating data manipulation: unexpected changes to survey metadata, responses, or link configurations from unknown IP addresses or without corresponding user actions. Implement logging around access control decisions in the survey handler. If available, deploy a web application firewall (WAF) rule to inspect requests to survey link endpoints for suspicious payloads or parameter tampering. Correlate logs with your identity and access management (IAM) system to identify sessions that should not have privilege to modify surveys.

Why prioritize this

This vulnerability merits medium priority based on its CVSS 6.5 score, remote exploitability without authentication, and direct impact on data integrity and availability. While not yet exploited in the wild (per KEV), the lack of authentication requirement means every exposed Formbricks 5.0.0 instance is a target. Prioritization should increase if your instance is internet-facing, used for sensitive data collection, or central to business processes. For internal-only deployments with restricted network access, remediation can follow standard patching schedules.

Risk score, explained

The CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L) reflects a network-adjacent attack that requires no privileges or user interaction but causes limited integrity and availability damage. The score of 6.5 is elevated by the absence of authentication and the low attack complexity, but constrained by the limited scope of impact (integrity and availability only; no confidentiality breach). Organizations with strict data integrity or availability requirements should treat this as HIGH priority despite the medium score.

Frequently asked questions

Do we need to upgrade immediately, or can we delay patching?

Upgrade within 2–4 weeks as part of your standard patch cycle, sooner if the instance is internet-facing. The remote, unauthenticated exploitability means every exposed instance is at risk. If you cannot patch immediately, apply network-level restrictions (firewall, IP allowlisting, VPN) to limit access to trusted networks.

Is version 5.1.0-rc.1 stable enough for production use?

Release Candidate versions typically contain all bug fixes and security patches but may lack the testing and stability guarantees of a final release. Review the Formbricks release notes and community feedback. If a stable version 5.1.0 or later is available, prefer that. If only the RC is available, test thoroughly in staging before production deployment.

What should I monitor after applying the patch?

After upgrading, verify that survey functionality operates normally and that historical data remains intact. Monitor logs for any access errors or unexpected behavior in the survey link handler. Continue watching for security advisories related to Formbricks, and maintain regular patching hygiene.

Does this vulnerability affect our hosted Formbricks instance?

If you use a Formbricks SaaS offering hosted by the vendor, the vendor is responsible for applying the patch. Confirm the vendor's patch status through their security advisories or support channels. If you self-host Formbricks, you are responsible for upgrading.

This vulnerability intelligence is provided for informational purposes. The information herein is derived from the CVE record published on 2026-07-06 and modified 2026-07-07. Always verify patch version numbers, commit hashes, and vendor advisories against official sources before deploying updates. Test patches in a non-production environment. SEC.co makes no warranty as to the accuracy, completeness, or timeliness of this information. Security assessments should be conducted by qualified professionals in consultation with your organization's risk and compliance teams. Source: NVD (public-domain), retrieved 2026-08-14. Analysis generated by SEC.co (claude-haiku-4-5).