Skip to content
Fencer Vulns
medium 5.3

CVE-2021-20282 json

Moodle Bypass email verification secret when confirming account registration

published 2021-03-15 5 y ago modified 2026-09-08 2 mo ago also BIT-moodle-2021-20282 , EUVD-2022-4000 , GHSA-grj4-g57c-9xmv

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits
0
none known

Summary

When creating a user account, it was possible to verify the account without having access to the verification email link/secret in moodle before 3.10.2, 3.9.5, 3.8.8, 3.5.17.

Patch / fix

  • packagist moodle/moodle 3.5.17, 3.8.8, 3.9.5, 3.10.2
  • bitnami moodle 3.5.17, 3.8.8, 3.9.5, 3.10.2
  • moodle moodle 3.5.17, 3.8.8, 3.9.5, 3.10.2

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-2021-20282 updated

moodle: Bypass email verification secret when confirming account registration

  • 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.32% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist moodle/moodle
>=3.5, <3.5.17
>=3.8, <3.8.8
>=3.9, <3.9.5
>=3.10, <3.10.2
3.5.17
3.8.8
3.9.5
3.10.2
bitnami moodle
>=3.5.0, <3.5.17
>=3.8.0, <3.8.8
>=3.9.0, <3.9.5
>=3.10.0, <3.10.2
3.5.17
3.8.8
3.9.5
3.10.2

Affected products

  • n/a moodle

Classification

Weakness

References

Sources

Fencer Vulns 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.