How severe is CVE-2012-6112?

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

Which packages are affected by CVE-2012-6112?

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

How do I fix CVE-2012-6112?

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2012-6112 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-6112 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2012-6112?

CVE-2012-6112 has an EPSS (Exploit Prediction Scoring System) score of 2.3%, placing it in the 83th 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-2012-6112?

CVE-2012-6112 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2012-6112 published, and has it been updated?

CVE-2012-6112 was published on January 27, 2013 and was last updated on April 10, 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

CVE-2012-6112 — moodle

Fix: tinymce/tinymce_spellchecker_php@2291018

CVE-2012-6112 is a CWE-264 vulnerability in moodle/moodle. A fix is available for moodle/moodle — see the affected versions and patch details below.

PHP Spellchecker addon for TinyMCE allows attackers to trigger arbitrary outbound HTTP requests

Also known asGHSA-fx5h-3786-h2w6

Published

Jan 27, 2013

Updated

Apr 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

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

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

classes/GoogleSpell.php in the PHP Spellchecker (aka Google Spellchecker) addon before 2.0.6.1 for TinyMCE, as used in Moodle 2.1.x before 2.1.10, 2.2.x before 2.2.7, 2.3.x before 2.3.4, and 2.4.x before 2.4.1 and other products, does not properly handle control characters, which allows remote attackers to trigger arbitrary outbound HTTP requests via a crafted string.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`moodle/moodle`	≥ 2.1.0&&< 2.1.10	2.1.10`composer require moodle/moodle:^2.1.10`
🐘Packagist	`moodle/moodle`	≥ 2.2.0&&< 2.2.7	2.2.7`composer require moodle/moodle:^2.2.7`
🐘Packagist	`moodle/moodle`	≥ 2.3.0&&< 2.3.4	2.3.4`composer require moodle/moodle:^2.3.4`
🐘Packagist	`moodle/moodle`	≥ 2.4.0&&< 2.4.1	2.4.1`composer require moodle/moodle:^2.4.1`

Affected Products

2 products · 33 configurations

Application

moodlemoodle

22 versions

2.1.02.1.12.1.22.1.32.1.42.1.52.1.62.1.72.1.82.1.92.2.02.2.1

Application

spellchecker phptinymce

5 versions

2.02.0.12.0.22.0.32.0.6

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.1.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-6112 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-6112 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works