# CVE-2026-10282: Bottelet DaybydayCRM DocumentsController.php view improper authorization

> Remote attackers can access documents without proper authorization in DaybydayCRM, requiring a patch to fix.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **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:** 1 Jun 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-9wcr-pjwm-2cv7

## What is CVE-2026-10282?

CVE-2026-10282 is a medium-severity missing authorization vulnerability in Bottelet DaybydayCRM, published on 1 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in Bottelet DaybydayCRM up to 2.2.1. This impacts the function view of the file app/Http/Controllers/DocumentsController.php. Such manipulation leads to improper authorization. The attack may be launched remotely. It is best practice to apply a patch to resolve this issue.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-10282 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10282 is a medium-severity missing authorization vulnerability in Bottelet DaybydayCRM, published on 1 Jun 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-10282 in the wild and no public exploit code.

Affected product: Bottelet DaybydayCRM. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-10282/ (Markdown: https://insights.sbomify.com/CVE-2026-10282/index.md)
```

## Sources

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

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