Live › vulnerability › CVE-2026-116008
Go to dashboardDaybydayCRM through 2.2.1 has a missing authorization check in the project assignment controller. Any authenticated employee can send a request to reassign a project to another user, bypassing the permission that should gate that action.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-24 12:47 UTC. All times on this page are UTC.
Teams that self-host DaybydayCRM at version 2.2.1 or earlier and have low-privileged employee accounts. The exposure comes from any logged-in user being able to call the project reassignment endpoint. Instances on a later release or without untrusted employee accounts are less exposed.
No product ranges from the sources yet.
2.2.1 are affected per the sourcesProjectsController::updateAssign() checks the can-assign-new-user-to-project permissionUnknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
DaybydayCRM through 2.2.1 contains a missing authorization vulnerability in ProjectsController::updateAssign() that allows any authenticated user to reassign projects without the can-assign-new-user-to-project permission. Low-privileged employees can send PATCH or POST requests to /projects/updateassign/{external_id} with a chosen user_assigned_id to redirect project ownership and notifications.
This page as .md · .json · in your agent: get_signal("CVE-2026-116008")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.