# CVE-2026-62235: Grav Flex-Objects < 1.4.3 Authorization Bypass via API

> Authenticated users with API access can perform unauthorized CRUD operations on directories lacking explicit permissions in the Grav Flex-Objects plugin.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA: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:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-gv8p-326f-p8gj

## What is CVE-2026-62235?

CVE-2026-62235 is a low-severity missing authorization vulnerability in getgrav grav, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Grav Flex-Objects before version 1.4.3 contains a broken access control vulnerability in the admin-next REST API that allows authenticated users with only api.access permission to perform unauthorized CRUD operations on permission-less directories. Attackers with api.access credentials can create, read, update, delete, and export objects from any directory lacking an explicit permissions configuration, bypassing intended authorization controls.

Weakness: CWE-862 (Missing Authorization), CWE-636 (Not Failing Securely)

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


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

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

## Is CVE-2026-62235 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62235 is a low-severity missing authorization vulnerability in getgrav grav, published on 17 Jul 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-62235 in the wild and no public exploit code.

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

## Sources

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

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