# CVE-2026-100672: grav-plugin-comments before 1.2.11 Unauthenticated Information Disclosure

> Unauthenticated attackers can access recent comment data including emails and file paths via an unprotected admin handler in the Grav Comments plugin.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-8rj9-9ch5-2f4r

## What is CVE-2026-100672?

CVE-2026-100672 is a high-severity missing authorization vulnerability in getgrav grav-plugin-comments, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Comments plugin (getgrav/grav-plugin-comments) for Grav CMS through version 1.2.10 registers an admin handler that returns comment data as JSON without any authentication check. The handler branches on isAdmin(), which only indicates that the admin service is registered on the current route rather than that the visitor is authenticated, and it echoes the JSON and calls exit() during the plugins stage, before the classic Admin plugin would render its login screen. On a site using the classic Admin plugin with Comments enabled (the default), an unauthenticated remote attacker can request /admin/comments/page:<n> (e.g. page:0.001) and retrieve every comment from the last 7 days, including each commenter's email address and the absolute server filesystem path of the data file. Sites running the Grav 2.0 Admin Next stack (admin2 + api) are not affected via this path. The issue is fixed in 1.2.11, which requires an authenticated user with admin.comments or admin.super and removes the absolute filePath from the response.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-100672 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100672 is a high-severity missing authorization vulnerability in getgrav grav-plugin-comments, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100672 exists.

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

## Sources

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

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