# CVE-2026-47236: Missing authorization in solidtime

> Employees without specific permissions can view pending invitation and member emails via the team page, bypassing API authorization checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 12 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-33xq-wf67-c7vh

## What is CVE-2026-47236?

CVE-2026-47236 is a medium-severity missing authorization vulnerability in solidtime-io solidtime, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Solidtime is an open-source time-tracking app. Prior to version 0.12.2, Solidtime defines an explicit invitations:view and members:view permissions that gates the official invitations and members API. The Jetstream web team page authorizes access with only belongsToTeam() and then loads and serializes all pending invitation emails as well as members into Inertia props. Any employee who belongs to the organization can read pending invitation email addresses and members through the serialised inertia data in the team page body even though the same user is forbidden from the API. This issue has been patched in version 0.12.2.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-47236 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47236 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47236 is a medium-severity missing authorization vulnerability in solidtime-io solidtime, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47236 exists.

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

## Sources

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

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