How severe is CVE-2024-47876?

No CVSS score has been assigned to CVE-2024-47876 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-47876?

CVE-2024-47876 affects the following packages: org.sakaiproject.kernel:sakai-kernel-impl (Maven). Ecosystems affected: Maven.

How do I fix CVE-2024-47876?

Update org.sakaiproject.kernel:sakai-kernel-impl to 23.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-47876 is resolved across your whole dependency graph.

How do I detect CVE-2024-47876 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.sakaiproject.kernel:sakai-kernel-impl. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2024-47876 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2024-47876?

O3 pinpoints whether CVE-2024-47876 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2024-47876 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-47876 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2024-47876?

CVE-2024-47876 is classified as CWE-285 (CWE-285), CWE-863 (CWE-863). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-47876 published, and has it been updated?

CVE-2024-47876 was published on October 15, 2024 and was last updated on July 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2024-47876

Fix: sakaiproject/sakai@a9aadd9

CVE-2024-47876 is a CWE-285 vulnerability in org.sakaiproject.kernel:sakai-kernel-impl. O3 Security confirms whether CVE-2024-47876 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Sakai: Kernel users created with type roleview can login as a normal user

Also known asGHSA-cx95-q6gx-w4qp

Published

Oct 15, 2024

Updated

Jul 15, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 15, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕org.sakaiproject.kernel:sakai-kernel-impl

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Sakai is a Collaboration and Learning Environment. Starting in version 23.0 and prior to version 23.2, kernel users created with type roleview can log in as a normal user. This can result in illegal access being granted to the system. Version 23.3 fixes this vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.sakaiproject.kernel:sakai-kernel-impl`	≥ 23.0&&< 23.3	23.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.sakaiproject.kernel:sakai-kernel-impl. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.sakaiproject.kernel:sakai-kernel-impl to 23.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-47876 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-47876 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-47876. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-47876 in your dependencies?

O3 detects CVE-2024-47876 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works