{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-77239 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-77239 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-77239 is a high-severity missing authorization vulnerability in ArnasDon wacrm, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-77239 and fix it if it is affected.\n\nWhat it is: CVE-2026-77239 is a high-severity missing authorization vulnerability in ArnasDon wacrm, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-77239 in the wild and no public exploit code.\n\nAffected product: ArnasDon wacrm. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-77239/ (Markdown: https://insights.sbomify.com/CVE-2026-77239/index.md)","id":"CVE-2026-77239","markdown":"https://insights.sbomify.com/CVE-2026-77239/index.md","name":"CVE-2026-77239","record":{"aliases":["GHSA-34q7-fv77-625j"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WhatsApp CRM template","requires_auth":"low_privilege","summary":"Attackers with viewer access can modify or delete workflows and trigger outbound actions due to missing role checks on service-role database writes.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"WACRM is a self-hostable CRM template for WhatsApp. In version 0.7.0 and earlier, WACRM flow and automation write routes authenticate account viewers but do not enforce the agent role before using a service-role database client that bypasses row-level security. In src/app/api/flows/[id]/route.ts, src/app/api/flows/[id]/activate/route.ts, and src/app/api/flows/route.ts, a viewer can create, edit, activate, or delete flows because membership-only checks are followed by service-role writes. In src/app/api/automations/route.ts and src/app/api/automations/engine/route.ts, a viewer can create active automations and trigger outbound WhatsApp actions without the role required by the underlying write policies. This can permit unauthorized workflow changes, destructive flow deletion, and outbound actions from a role intended to be read-only. This vulnerability is fixed with commit 03e851bea56dcf6bb21ff1b80ba531372bf3269f.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"WACRM: Service-role routes missing a role check","id":"CVE-2026-77239","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"WACRM: Database-layer authorization bypasses","id":"CVE-2026-77240"},"packages":[],"prev":{"headline":"Missing type validation in xQueueAddToSet in FreeRTOS-Kernel","id":"CVE-2026-77237"},"products":["wacrm"],"published":"2026-09-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-18","vendors":["ArnasDon"]},"summary":"Attackers with viewer access can modify or delete workflows and trigger outbound actions due to missing role checks on service-role database writes.","url":"https://insights.sbomify.com/CVE-2026-77239/"}