dbcve.org
MaharaApplication

CVE-2024-47192

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-26
Fix available
A fix is available. Upgrade to 23.04.9 / 24.04.5 or later.
See remediation →
62/100
Remediation priority · Elevated
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
An issue was discovered in Mahara 23.04.8 and 24.04.4. The use of a malicious export download URL can allow an attacker to download files that they do not have permission to download.

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 23.04.8 and 24.04.4 contain an authorization bypass vulnerability in the export download functionality. Attackers can craft malicious export download URLs to access files they do not have permission to view, exploiting insufficient authorization checks in the file export mechanism.

MitigationUpgrade to Mahara versions 23.04.9 or 24.04.5 or later to obtain the security patch. Alternatively, review and restrict access controls on the export download handler until the patch can be applied.

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.9>= 24.04.0, < 24.04.5

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Identify installed Mahara version
    Check the version by locating the version.php file in the Mahara htdocs directory, or access the admin panel and navigate to Site options to view the installed version number
    Affected if The installed version is less than 23.04.9, or is 24.04.0 through 24.04.4 (the system is not patched)
  2. Confirm export feature is accessible
    Verify that the export functionality is enabled in Mahara configuration by checking if users have export permissions, or attempt to access an export download URL pattern such as /export/download/ to see if the endpoint responds
    Affected if The export download endpoint is reachable and functional in the environment

The environment is affected if the installed Mahara version is within the vulnerable ranges AND the export download functionality is enabled and accessible to users.

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.9 / 24.04.5 or later
Fixed in 23.04.924.04.5
Interim mitigation

Upgrade to Mahara versions 23.04.9 or 24.04.5 or later to obtain the security patch. Alternatively, review and restrict access controls on the export download handler until the patch can be applied.

Recommended fix High confidence

23.04.9 (for 23.x branch) or 24.04.5 (for 24.x branch)

  1. 1. Backup your Mahara database and files directory before upgrading
  2. 2. Download the appropriate Mahara version from the official Mahara website (mahara.org)
  3. 3. If upgrading from Mahara 23.x to 24.x: Review the Mahara release notes for breaking changes and ensure your plugins/themes are compatible
  4. 4. Place your Mahara instance into maintenance mode via the admin interface or by creating a file called 'suspended.html' in the htdocs directory
  5. 5. Replace the existing Mahara application files with the new version files, preserving your config.php and any custom local code
  6. 6. Run the database upgrade script by accessing the site URL (the upgrade will trigger automatically)
  7. 7. Verify the upgrade was successful by logging in and checking the admin dashboard shows the correct version
  8. 8. Test the export/download functionality to confirm the vulnerability is resolved
Caveat Major version upgrades (e.g., 23.x to 24.x) may introduce breaking changes; review release notes and test plugins/themes for compatibility before production upgrade

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

Fix this in Mahara Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47192 — 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-47192 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