Is CVE-2016-7038 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2016-7038 being exploited in the wild.

How severe is CVE-2016-7038?

High severity, with a CVSS score of 7.3, published 20 January 2017.

Which products and versions are affected?

Moodle 2.x, 3.x; moodle/moodle (Packagist) ECOSYSTEM:introduced=2.7,fixed=2.7.16.

Is there a fix for CVE-2016-7038?

Yes. moodle/moodle (Packagist): upgrade to 2.7.16 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2016-7038 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2016-7038?

Check whether you run Moodle or moodle/moodle (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2016-7038: Moodle web service token invalidation failure on password change

CVE-2016-7038 · Severity: high · CVSS 7.3 · Published 2017-01-20

Moodle, a widely used learning management system, contains a security flaw where web service access tokens remain active even after a user changes their password. This means that if an unauthorized person or device has obtained a token, they can continue to access the user's account and data even after the user attempts to secure the account by updating their credentials. This could lead to persistent unauthorized access to student or teacher information.

Technologies: Moodle, moodle/moodle (Packagist). Vendors: Moodle, Packagist.

Quick answers

Is CVE-2016-7038 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-7038 being exploited in the wild.
How severe is CVE-2016-7038?: High severity, with a CVSS score of 7.3, published 20 January 2017.
Which products and versions are affected?: Moodle 2.x, 3.x; moodle/moodle (Packagist) ECOSYSTEM:introduced=2.7,fixed=2.7.16.
Is there a fix for CVE-2016-7038?: Yes. moodle/moodle (Packagist): upgrade to 2.7.16 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2016-7038 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2016-7038?: Check whether you run Moodle or moodle/moodle (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

moodle/moodle (Packagist): upgrade to 2.7.16 or later
```
composer require moodle/moodle:^2.7.16
```

Technical details

A session management vulnerability exists in Moodle versions 2.x and 3.x where the application fails to revoke or invalidate active web service tokens during a password change event. This includes both user-initiated password changes and administrative forced password resets. An attacker who has previously compromised a web service token can maintain persistent access to the API and user data regardless of credential updates. The vulnerability is categorized under CWE-640 (Weak Password Recovery Mechanism) and allows for continued unauthorized interaction with the platform's web services. Patches have been released by the vendor to address this behavior.

Affected products

Moodle Moodle 2.x, 3.x

Identifiers

CVE-2016-7038
GHSA-2phx-w35g-x9vm

Timeline

2016-09-26: advisory: Initial vendor advisory and security focus BID published
2017-01-20: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.