Skip to content
Fencer Intel
medium 6.5

CVE-2013-1836 json

Moodle does not properly manage privileges for WebDAV repositories

published 13y ago modified 4mo ago also GHSA-664q-mrxx-2x2v , EUVD-2022-2722

cvss
6.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

Moodle 2.x through 2.1.10, 2.2.x before 2.2.8, 2.3.x before 2.3.5, and 2.4.x before 2.4.2 does not properly manage privileges for WebDAV repositories, which allows remote authenticated users to read, modify, or delete arbitrary site-wide repositories by leveraging certain read access.

Patch / fix

  • packagist moodle/moodle 2.2.8, 2.3.5, 2.4.2

Is CVE-2013-1836 in your dependencies? 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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-1836 updated cvss 4.0

moodle: Unauthorized settings editing through WebDav repository (MSA-13-0019)

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
packagist moodle/moodle
>=2.0.0, <2.2.8
>=2.3.0, <2.3.5
>=2.4.0, <2.4.2
2.2.8
2.3.5
2.4.2

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

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.