How severe is CVE-2013-3630?

No CVSS score has been assigned to CVE-2013-3630 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-3630?

CVE-2013-3630 affects the following packages: moodle/moodle (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2013-3630?

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

How do I detect CVE-2013-3630 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-2013-3630 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-2013-3630 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2013-3630, including 1 documented proof-of-concept exploit on Exploit-DB and 3 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-2013-3630?

CVE-2013-3630 has an EPSS (Exploit Prediction Scoring System) score of 41.7%, placing it in the 99th 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-2013-3630?

CVE-2013-3630 is classified as Code Injection (CWE-94). 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.

Is there exploit tooling available for CVE-2013-3630?

2 Metasploit modules reference CVE-2013-3630, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2013-3630 published, and has it been updated?

CVE-2013-3630 was published on May 13, 2022 and was last updated on December 2, 2024. 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

CVE-2013-3630 — moodle

CVE-2013-3630 is a Code Injection vulnerability in moodle/moodle. 4 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 Authenticated Spelling Binary Remote Code Execution

Published

May 13, 2022

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

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

EPSS Exploitation Probability

via FIRST.org ↗

41.7%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐘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 through 2.5.2 allows remote authenticated administrators to execute arbitrary programs by configuring the aspell pathname and then triggering a spell-check operation within the TinyMCE editor.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`moodle/moodle`	all versions	2.5.3`composer require moodle/moodle:^2.5.3`

Affected Products

1 product · 116 configurations

Application

moodlemoodle

≤ 2.5.2

115 versions

1.1.11.2.01.2.11.3.01.3.11.3.21.3.31.3.41.4.11.4.21.4.31.4.4

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-29324remotelinux✓ Verified

Moodle - Remote Command Execution (Metasploit)

by Metasploit · Oct 31, 2013

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.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-3630 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

Moodle through 2.5.2 allows remote authenticated administrators to execute arbitrary programs by configuring the aspell pathname and then triggering a spell-check operation within the TinyMCE editor.

O3 Security · Impact-Aware SCA

Is CVE-2013-3630 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works