Skip to content
Fencer Intel
medium 5.0

CVE-2012-6112 json

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

published 2013-01-27 13 y ago modified 2026-06-16 4 mo ago also GHSA-fx5h-3786-h2w6 , EUVD-2022-3849

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist moodle/moodle 2.1.10, 2.2.7, 2.3.4, 2.4.1
  • wordpress Debian 14, Debian 13, Debian 12 3.5.1+dfsg-2

debian advisories DEBIAN-CVE-2012-6112

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-6112 updated cvss 5.0

Spellchecker): Control characters not sanitized properly from $lang and $str arguments in _getMatches

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.29% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
packagist moodle/moodle
>=2.1.0, <2.1.10
>=2.2.0, <2.2.7
>=2.3.0, <2.3.4
>=2.4.0, <2.4.1
2.1.10
2.2.7
2.3.4
2.4.1

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.