DaybydayCRM through 2.2.1 Missing Authorization via ProjectsController updateAssign
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fix or patch referenced
- 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
DaybydayCRM, a customer relationship management application, up to and including version 2.2.1, is affected. Any logged-in user, including low-privileged employees, can reassign projects to other users without having the required permission, which lets them redirect project ownership and the notifications that go with it.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Bottelet DaybydayCRM
through 2.2.1