# CVE-2026-38529: Webkul Krayin CRM has Broken Object-Level Authorization (BOLA) in the /Settings/UserController.php

> Authenticated attackers can reset arbitrary user passwords and take over accounts via a Broken Object-Level Authorization flaw in the settings controller.

- **Severity:** High 8.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-r8rp-5f55-5j9x

## What is CVE-2026-38529?

CVE-2026-38529 is a high-severity missing authorization vulnerability in n/a, published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Broken Object-Level Authorization (BOLA) in the /Settings/UserController.php endpoint of Webkul Krayin CRM v2.2.x allows authenticated attackers to arbitrarily reset user passwords and perform a full account takeover via supplying a crafted HTTP request.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-38529?

2 open source packages ship an affected version, including krayin/laravel-crm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `krayin/laravel-crm` | Packagist | All versions to 2.2.0 | None |
| `krayin/laravel-crm` | Packagist | All versions to 2.2.0 | None |

Products: Webkul Krayin Crm.

## How do I fix CVE-2026-38529?

No fix has been published for CVE-2026-38529 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-38529 being exploited?

There is no known exploitation of CVE-2026-38529 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-46367](https://insights.sbomify.com/CVE-2024-46367/): Cross-site scripting in n/a (critical 9.6)
- [CVE-2024-46366](https://insights.sbomify.com/CVE-2024-46366/): Cross-site scripting in n/a (high 8.8)
- [CVE-2026-38530](https://insights.sbomify.com/CVE-2026-38530/): Webkul Krayin CRM has Broken Object-Level Authorization (BOLA) in the /Controllers/Lead/LeadController.php (high 8.1)
- [CVE-2026-38532](https://insights.sbomify.com/CVE-2026-38532/): Webkul Krayin CRM has Broken Object-Level Authorization (BOLA) in the /Contact/Persons/PersonController.php (high 8.1)
- [CVE-2024-45932](https://insights.sbomify.com/CVE-2024-45932/): Krayin CRM vulnerable to Cross Site Scripting (XSS) via the organization name (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-38529 and fix it if it is affected.

What it is: CVE-2026-38529 is a high-severity missing authorization vulnerability in n/a, published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-38529 in the wild and no public exploit code.

Affected packages and fixed versions:
- krayin/laravel-crm (Packagist): affected all versions up to 2.2.0; no fix listed
- krayin/laravel-crm (Packagist): affected all versions up to 2.2.0; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-38529/ (Markdown: https://insights.sbomify.com/CVE-2026-38529/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-38529
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-38529
- OSV: https://osv.dev/vulnerability/CVE-2026-38529

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-38529/
Summaries are generated and may contain mistakes; the official description above is the record.