# CVE-2026-19417: KiviCare < 4.5.4 - Patient+ Arbitrary Media Attachment Read via IDOR

> Authenticated patients can download any media file, including other patients' medical reports, due to missing authorization checks.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A: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:** 19 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-34m6-mf7c-4crh

## What is CVE-2026-19417?

CVE-2026-19417 is a medium-severity missing authorization vulnerability in Unknown KiviCare, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The KiviCare  WordPress plugin before 4.5.4 does not verify that the requesting user is entitled to the media file being served, allowing authenticated patient-level users to download any file in the media library, including other patients' uploaded medical reports.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-19417 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19417 is a medium-severity missing authorization vulnerability in Unknown KiviCare, published on 19 Aug 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-19417 in the wild and no public exploit code.

Affected product: Unknown KiviCare. 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-19417/ (Markdown: https://insights.sbomify.com/CVE-2026-19417/index.md)
```

## Sources

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

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