# CVE-2026-115972: FaveoSuite Faveo Helpdesk UnAuthController.php UnAuthController.resolve authorization


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-4h5m-x643-3937

## What is CVE-2026-115972?

CVE-2026-115972 is a medium-severity vulnerability in FaveoSuite Faveo Helpdesk, published on 24 Oct 2026. 

### Official description

A vulnerability was determined in FaveoSuite Faveo Helpdesk up to 2.0.3. Affected by this vulnerability is the function UnAuthController.changeStatus/UnAuthController.close/UnAuthController.open/UnAuthController.resolve of the file app/Http/Controllers/Client/helpdesk/UnAuthController.php. Executing a manipulation of the argument id/status can lead to missing authorization. The attack can be launched remotely. The vendor was contacted early about this disclosure.

Weakness: CWE-863 (Incorrect Authorization), CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-115972 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115972 is a medium-severity vulnerability in FaveoSuite Faveo Helpdesk, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115972 in the wild and no public exploit code.

Affected product: FaveoSuite Faveo Helpdesk. 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-115972/ (Markdown: https://insights.sbomify.com/CVE-2026-115972/index.md)
```

## Sources

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

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