How severe is CVE-2017-2641?

CVE-2017-2641 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-2641?

CVE-2017-2641 affects the following packages: moodle/moodle (Packagist), moodle/moodle (Packagist), moodle/moodle (Packagist), moodle/moodle (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2017-2641?

Update moodle/moodle to 2.7.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-2641 is resolved across your whole dependency graph.

How do I detect CVE-2017-2641 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for moodle/moodle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-2641 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2017-2641 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2017-2641, including 1 documented proof-of-concept exploit on Exploit-DB and 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-2641?

CVE-2017-2641 has an EPSS (Exploit Prediction Scoring System) score of 14.5%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2017-2641?

CVE-2017-2641 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2017-2641 published, and has it been updated?

CVE-2017-2641 was published on March 26, 2017 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

CVE-2017-2641 — moodle

CRITICAL

CVE-2017-2641 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in moodle/moodle. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for moodle/moodle — see the affected versions and patch details below.

Moodle SQL injection via user preferences

Also known asGHSA-xhq3-455r-xv44

Published

Mar 26, 2017

Updated

Oct 24, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

3 known

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

14.5%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐘moodle/moodle🐘moodle/moodle🐘moodle/moodle🐘moodle/moodle

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

In Moodle 2.x and 3.x, SQL injection can occur via user preferences.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`moodle/moodle`	≥ 2.7&&< 2.7.19	2.7.19`composer require moodle/moodle:^2.7.19`
🐘Packagist	`moodle/moodle`	≥ 3.0&&< 3.0.9	3.0.9`composer require moodle/moodle:^3.0.9`
🐘Packagist	`moodle/moodle`	≥ 3.1&&< 3.1.5	3.1.5`composer require moodle/moodle:^3.1.5`
🐘Packagist	`moodle/moodle`	≥ 3.2&&< 3.2.2	3.2.2`composer require moodle/moodle:^3.2.2`

Affected Products

1 product · 52 configurations

Application

moodlemoodle

35 versions

2.7.02.7.12.7.22.7.32.7.42.7.52.7.62.7.72.7.82.7.92.7.102.7.11

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-41828webappsphp

Moodle 2.x/3.x - SQL Injection

by Marko Belzetski · Apr 6, 2017

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for moodle/moodle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update moodle/moodle to 2.7.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-2641 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

In Moodle 2.x and 3.x, SQL injection can occur via user preferences.

O3 Security · Impact-Aware SCA

Is CVE-2017-2641 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-89SQL Injection

Weaponization

No Nuclei template or Metasploit module yet. 3 public proof-of-concept references are listed on this page.

OpenSSF Scorecard

Package health score

moodle

3.4/10

Code-Review0/10

Maintained10/10

Branch-Protection0/10

Assessed Oct 26, 2026

Timeline

Disclosed

Mar 26, 2017

First exploit

Apr 6, 2017

Last updated

Oct 24, 2026

Identifiers

CVE-2017-2641

GHSA-xhq3-455r-xv44

References

Advisorysecurityfocus.com Advisorynvd.nist.gov · CVE 2017 2641 Fixmoodle.org · discuss Websecuritytracker.com Webexploit-db.com Webexploit-db.com Packagegithub.com · moodle

Related vulnerabilities

This CVE is critical severity — higher than any of the other 8 CVEs affecting moodle/moodle (highest there: high).

CVE-2026-26047CVE-2026-26045CVE-2025-67853CVE-2025-67850CVE-2025-67857CVE-2025-67856CVE-2025-67848CVE-2025-67849

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2017-2641 — moodle

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2017-2641 in your dependencies?