CVE-2023-5356

HIGHNVD 7.3
7.3

Incorrect authorization checks in GitLab CE/EE from all versions starting from 8.13 before 16.5.6, all versions starting from 16.6 before 16.6.4, all versions starting from 16.7 before 16.7.2, allows a user to abuse slack/mattermost integrations to execute slash commands as another user.

CVSS v3
7.3
EG Score
EPSS
KEV
Not listed

Published

January 12, 2024

Last Modified

November 21, 2024

Vendor Advisories for CVE-2023-5356(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Frequently asked(4)

What is CVE-2023-5356?
CVE-2023-5356 is a high vulnerability published on January 12, 2024. Incorrect authorization checks in GitLab CE/EE from all versions starting from 8.13 before 16.5.6, all versions starting from 16.6 before 16.6.4, all versions starting from 16.7 before 16.7.2, allows a user to abuse slack/mattermost integrations to execute slash commands as another user.
When was CVE-2023-5356 disclosed?
CVE-2023-5356 was first published in the National Vulnerability Database on January 12, 2024, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2023-5356?
CVE-2023-5356 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2023-5356?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-5356, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-5356

Explore →

Is Your Infrastructure Affected by CVE-2023-5356?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.