Mahara before 1.5.12, 1.6.x before 1.6.7, and 1.7.x before 1.7.3 does not properly restrict access to artefacts, which allows remote authen…

published 2014-05-19 12y ago modified 2026-06-16 4mo ago also EUVD-2013-4306

cvss: 4.0; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits: 0; none known

Mahara before 1.5.12, 1.6.x before 1.6.7, and 1.7.x before 1.7.3 does not properly restrict access to artefacts, which allows remote authenticated users to read arbitrary artefacts via the (1) artefact id in an upload action when creating a journal or (2) instconf_artefactid_selected[ID] parameter in an upload action when editing a block.

Is CVE-2013-4429 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.11% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	2.0	4.0	AV:N/AC:L/Au:S/C:P/I:N/A:N

Classification

Weakness

CWE-264 Permissions, Privileges, and Access Controls

References

mahara.org /interaction/forum/topic.php?id=5753
openwall.com /lists/oss-security/2013/10/08/3
mailing-list
openwall.com /lists/oss-security/2013/10/15/1
mailing-list
bugs.launchpad.net /mahara/+bug/1211758
openwall.com /lists/oss-security/2013/10/16/7
mailing-list

Sources

CVE List CVE-2013-4429
NVD CVE-2013-4429

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.