CVE-2024-47853
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in Mahara 23.04.8 and 24.04.4. Attackers may utilize escalation of privileges in certain cases when logging into Mahara with Learning Tools Interoperability (LTI).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMahara versions 23.04.8 and 24.04.4 contain a privilege escalation vulnerability in the Learning Tools Interoperability (LTI) authentication mechanism, allowing attackers to gain elevated privileges during LTI login.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 23.04.9>= 24.04.0, < 24.04.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Mahara versionLocate the version file or admin interface (typically at /admin/registrations.php or in the Mahara version file included in the installation)Affected if The version is less than 23.04.9 OR greater than or equal to 24.04.0 but less than 24.04.5
-
Verify LTI authentication is configuredCheck the Mahara administration panel for Learning Tools Interoperability settings under Authentification or LTI provider configurationAffected if LTI authentication is enabled and configured as an external authentication method
-
Inspect LTI role mapping settingsReview the LTI role mapping configuration in the Mahara admin interface under LTI consumer settingsAffected if Role mappings assign elevated or administrative privileges to LTI users without manual review
You are affected if your Mahara version falls within the vulnerable range AND LTI authentication is enabled with role mappings that grant elevated privileges.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped23.04.924.04.5
Upgrade Mahara to a patched version beyond 23.04.8 and 24.04.4. Review LTI role mapping configuration to ensure only appropriate permissions are assigned during LTI authentication.
Mahara 23.04.9 (for 23.x branch) or 24.04.5 (for 24.x branch)
- 1. Identify the currently installed Mahara version by checking the version.php file or admin interface
- 2. If running 23.04.x (below 23.04.9): Upgrade to Mahara 23.04.9 or later
- 3. If running 24.04.x (below 24.04.5): Upgrade to Mahara 24.04.5 or later
- 4. After upgrade, verify the LTI authentication configuration still works correctly
- 5. Test that privilege escalation is no longer possible through LTI login
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47853 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47853 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data