In CLA-Assistant, versions before 2.8.5, due to improper access control an authenticated user could access API endpoints which are not inte…

published 2021-01-12 5y ago modified 2026-06-17 4mo ago also EUVD-2021-8745

cvss: 6.5; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits: 0; none known

In CLA-Assistant, versions before 2.8.5, due to improper access control an authenticated user could access API endpoints which are not intended to be used by the user. This could impact the integrity of the application.

Patch / fix

fixed in 1

sap cla-assistant 2.8.5

Is CVE-2021-21471 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.74% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	6.5	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
NVD	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
NVD	2.0	4.0	AV:N/AC:L/Au:S/C:N/I:P/A:N

Affected products

SAP SE CLA-Assistant

References

github.com /cla-assistant/cla-assistant/security/advisories/GHSA-4h6f-c68c-pxhr
third-party-advisory

Sources

CVE List CVE-2021-21471
NVD CVE-2021-21471

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.