dbcve.org
MaharaApplication

CVE-2024-39335

CRITICAL · 9.1 CVSS v3.1 Published 2025-08-26
Fix available
A fix is available. Upgrade to 23.04.6 / 24.04.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Supported versions of Mahara 24.04 before 24.04.1 and 23.04 before 23.04.6 are vulnerable to information being disclosed to an institution administrator under certain conditions via the 'Current submissions' page: Administration -> Groups -> Submissions.

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 confidence

Mahara versions 24.04 before 24.04.1 and 23.04 before 23.04.6 contain an information disclosure vulnerability where institution administrators can view sensitive information they should not have access to through the 'Current submissions' page (Administration -> Groups -> Submissions). The authorization logic fails to properly restrict data visibility based on institutional permissions.

MitigationUpgrade to Mahara 24.04.1 or 23.04.6 or later to patch the authorization bypass in the submissions page.

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
MaharaApplication
Affected:>= 23.04.0, < 23.04.6>= 24.04.0, < 24.04.1

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Mahara version
    Log into the Mahara instance as an administrator and navigate to Site Administration -> Configuration -> Version, or check the VERSION file in the Mahara installation directory.
    Affected if The installed version is 23.04.0 through 23.04.5, or 24.04.0.
  2. Confirm user has institution administrator role
    Navigate to Administration -> Institutions, or check the roles assigned to your user account. An institution administrator manages a specific institution but should not have system-wide admin privileges.
    Affected if Your account has the role of 'Institution administrator' for one or more institutions, rather than being a global Site administrator.
  3. Check for multiple institutions
    Navigate to Administration -> Institutions to view all configured institutions in the system.
    Affected if More than one institution is configured in the Mahara instance.
  4. Verify access to Submissions page
    Navigate to Administration -> Groups -> Submissions. This is the 'Current submissions' page where the authorization bypass occurs.
    Affected if As an institution administrator, you can access this page and view submission data.
  5. Confirm sensitive data exposure
    On the Submissions page (Administration -> Groups -> Submissions), check if you can view submission details, user profiles, or files belonging to institutions you do not administer.
    Affected if An institution administrator can view submissions, personal information, or artifacts from institutions other than the ones they administer.

You are affected if your Mahara installation is version 23.04.0-23.04.5 or 24.04.0, you have an institution administrator account, multiple institutions exist, and the Submissions page reveals data from other institutions that you should not be able to see.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 23.04.6 / 24.04.1 or later
Fixed in 23.04.624.04.1
Interim mitigation

Upgrade to Mahara 24.04.1 or 23.04.6 or later to patch the authorization bypass in the submissions page.

Recommended fix High confidence

Mahara 23.04.6 for 23.04.x branches; Mahara 24.04.1 for 24.04.0

  1. Identify the currently installed Mahara version by checking the version file or admin interface
  2. If running Mahara 23.04.x (where x < 6), plan upgrade to version 23.04.6
  3. If running Mahara 24.04.0, plan upgrade to version 24.04.1
  4. Review Mahara upgrade documentation for your deployment method (package manager or manual)
  5. Backup the Mahara database and files before upgrading
  6. Apply the upgrade following standard Mahara upgrade procedures
  7. Verify the upgrade was successful by checking the version number in the admin interface
  8. Confirm the vulnerability is resolved by accessing the 'Current submissions' page as an institution administrator
Caveat Review Mahara release notes for any breaking changes between minor versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mahara Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39335 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-39335 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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