Krayin CRM before 2.2.8 Broken Object Level Authorization via Lead Tag Attach/Detach
- Exploited
- No known exploitation
- Fix
- Fixed in 2.2.8
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.2.8.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 8/100 · provisional
- 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
Krayin CRM, a customer relationship management application, has a flaw in how it handles tag changes on leads: users with limited data access can add or remove tags on leads owned by others outside their scope. An attacker who can reach the application over the network and log in with a low-privilege account can alter these tags, though the bug does not expose lead data.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Krayin CRM before 2.2.8 contains a broken object level authorization vulnerability in Lead TagController attach and detach actions that skip the data-scope check. Authenticated users restricted to individual or group data scope can add or remove tags on leads owned by users outside their scope.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.2.8.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- krayin laravel-crm
fixed in 2.2.8
Evidence 6
- Patch
- Patch
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125374
Is CVE-2026-125374 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-125374?
laravel-crm: before 2.2.8.Source: cve.now feed data
How do I fix CVE-2026-125374?
Upgrade to a fixed version: 2.2.8.Source: cve.now feed data