# CVE-2026-10285: DevaslanPHP project-management Ticket KanbanScrumHelper.php recordUpdated improper authorization

> Remote attackers can bypass authorization checks in the Ticket KanbanScrumHelper to modify ticket records without proper permissions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/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:** 2 Jun 2026
- **Also known as:** GHSA-9xj7-hrc2-w62q

## What is CVE-2026-10285?

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

### Official description

A vulnerability has been found in DevaslanPHP project-management up to 2.0.0-beta1. Affected by this issue is the function KanbanScrumHelper::recordUpdated of the file app/Helpers/KanbanScrumHelper.php of the component Ticket Handler. The manipulation leads to improper authorization. The attack is possible to be carried out remotely. The project was informed of the problem early through an issue report but has not responded yet.

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

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


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

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

## Is CVE-2026-10285 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10285 is a medium-severity missing authorization vulnerability in DevaslanPHP project-management, 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-10285 in the wild and no public exploit code.

Affected product: DevaslanPHP project-management. 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-10285/ (Markdown: https://insights.sbomify.com/CVE-2026-10285/index.md)
```

## Sources

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

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