Menu

Star on GitHub · 3.2k

CVE-2010-1616

4.0 · MEDIUM

Moodle 1.8.x and 1.9.x before 1.9.8 can create new roles when restoring a course, which allows teachers to create new accounts even if they do not have the moodle/user:create capability.

Published Apr 29, 2010moodleEPSS 1.17%

Overview

CVE-2010-1616 is a medium-severity vulnerability affecting moodle moodle. It was published on April 29, 2010 and has a CVSS 2.0 base score of 4.0 (MEDIUM).

This vulnerability has a CVSS 2.0 base score of 4.0, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

Moodle 1.8.x and 1.9.x before 1.9.8 can create new roles when restoring a course, which allows teachers to create new accounts even if they do not have the moodle/user:create capability.

Remediation

Check the references section for vendor advisories and patches from moodle. Update moodle to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2010-1616?

CVE-2010-1616 is a medium-severity vulnerability affecting moodle moodle. It was published on April 29, 2010 and has a CVSS 2.0 base score of 4.0 (MEDIUM).

How severe is CVE-2010-1616?

This vulnerability has a CVSS 2.0 base score of 4.0, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2010-1616?

Check the references section for vendor advisories and patches from moodle. Update moodle to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2010-1616?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2010-1616 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2010

View all