What is the CVSS score of EUVD-2026-60546?

EUVD-2026-60546 has a CVSS 3.1 base score of 9.1 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.1%.

Which versions of Mahara are affected by EUVD-2026-60546?

Mahara ePortfolio deployments contain a path traversal vulnerability (CVSS 9.1) allowing unauthorized access to other users' private files and content, undermining the platform's access control…

How to fix or mitigate EUVD-2026-60546?

Within 24 hours, identify and audit all Mahara instances currently in operation, noting their version numbers and deployment scope. Within 7 days, upgrade Mahara to version 25.04.5 (for 25.x deployments) or 26.04.0 (for 26.x deployments), completing testing in non-production environments before each production update. Within 30 days, review access logs from the past 90 days for evidence of path traversal exploitation, document any suspicious file access patterns, and notify affected users of any confirmed unauthorized access.

Mahara EUVD-2026-60546

| CVE-2026-42162 CRITICAL

Path Traversal (CWE-22)

2026-08-17 mitre

GHSA-wj88-f77v-46px

Path Traversal N A

9.1

CVSS 3.1 · Vendor: mitre

Severity by source

Vendor (mitre) PRIMARY

9.1 CRITICAL

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

vuln.today AI

5.3 MEDIUM

Description is disclosure-only so I:N/A:N with C:H; 'certain circumstances' implies AC:H, and typical login-gated Mahara access plus needing a page/artefact context implies PR:L.

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

4.0 AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Analysis Generated

Aug 18, 2026 - 13:25 vuln.today

CVSS changed

Aug 18, 2026 - 13:22 NVD

9.1 (CRITICAL)

CVE Published

Aug 17, 2026 - 00:00 cve.org

CRITICAL 9.1

CVE Published

Aug 17, 2026 - 00:00 cve.org

UNKNOWN (no severity yet)

DescriptionCVE.org

Mahara before 25.04.5 and 26.04.0 is vulnerable to artefacts being accessible to others under certain circumstances when the file path to an artefact in a page is manipulated.

AnalysisAI

Improper access control via path traversal in Mahara's ePortfolio system allows others to reach artefacts (uploaded files/content) they should not see when the file path to an artefact embedded in a page is manipulated. It affects Mahara releases before 25.04.5 and before 26.04.0 and is fixed in those versions. No public exploit identified at time of analysis, and it is not listed in CISA KEV; the impact is unauthorized disclosure of user-owned content rather than server compromise.

Technical ContextAI

Mahara is an open-source ePortfolio and social-networking platform widely used in education for storing and sharing learner-created artefacts (files, images, documents) organized into pages. The flaw is classified as CWE-22 (Improper Limitation of a Pathname to a Restricted Directory / path traversal): when a page references an artefact by file path, that path can be manipulated so Mahara's access-control checks are bypassed and the underlying artefact is served to a requester who lacks legitimate permission. The CPE data supplied is a placeholder ('cpe:2.3:a:n/a:n/a:*') and provides no additional product/version precision beyond the vendor's own version statement.

RemediationAI

Vendor-released patch: upgrade to Mahara 25.04.5 or 26.04.0 (or later), the fixed versions named in the advisory at https://mahara.org/interaction/forum/topic.php?id=10057. If immediate upgrade is not possible, compensating controls include restricting the Mahara instance to authenticated users behind SSO/VPN to limit who can probe artefact paths, and reviewing web-server/proxy logs for anomalous requests to artefact/download endpoints containing path-traversal patterns (encoded '../' sequences); note these are detection/exposure-reduction measures only and do not close the underlying access-control gap, so they should not substitute for the patch. Because the flaw discloses user data, also consider whether previously exposed artefacts require breach-notification review once the fix is applied.