How severe is CVE-2018-14630?

CVE-2018-14630 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-14630?

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

How do I fix CVE-2018-14630?

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

How do I detect CVE-2018-14630 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-2018-14630 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2018-14630 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2018-14630, including 2 in-the-wild exploitations 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-2018-14630?

CVE-2018-14630 has an EPSS (Exploit Prediction Scoring System) score of 4.6%, placing it in the 92th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2018-14630?

CVE-2018-14630 is classified as Improper Input Validation (CWE-20), Code Injection (CWE-94). These weakness types 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-2018-14630 published, and has it been updated?

CVE-2018-14630 was published on September 17, 2018 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

HIGH severity

CVE-2018-14630 — moodle

HIGHFix: moodle/moodle@09cbca8

CVE-2018-14630 is a high-severity (CVSS 8.8) Improper Input Validation vulnerability in moodle/moodle. 2 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 XML import of ddwtos could lead to intentional remote code execution

Also known asGHSA-c3pr-h96w-2jjg

Published

Sep 17, 2018

Updated

Oct 24, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

4.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs92th percentile — riskier than 92% 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

moodle before versions 3.5.2, 3.4.5, 3.3.8, 3.1.14 is vulnerable to an XML import of ddwtos could lead to intentional remote code execution. When importing legacy 'drag and drop into text' (ddwtos) type quiz questions, it was possible to inject and execute PHP code from within the imported questions, either intentionally or by importing questions from an untrusted source.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`moodle/moodle`	≥ 3.5.0&&< 3.5.2	3.5.2`composer require moodle/moodle:^3.5.2`
🐘Packagist	`moodle/moodle`	≥ 3.4.0&&< 3.4.5	3.4.5`composer require moodle/moodle:^3.4.5`
🐘Packagist	`moodle/moodle`	≥ 3.2.0&&< 3.3.8	3.3.8`composer require moodle/moodle:^3.3.8`
🐘Packagist	`moodle/moodle`	all versions	3.1.14`composer require moodle/moodle:^3.1.14`

Affected Products

1 product · 5 configurations

Application

moodlemoodle

≥ 3.5.0 && ≤ 3.0.10

range

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.

moodle before versions 3.5.2, 3.4.5, 3.3.8, 3.1.14 is vulnerable to an X…

sec-consult.comNVDOct 2019

Report on seclists.org

seclists.orgNVDOct 2019

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 3.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-14630 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-14630 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works