CVE-2011-4959 json
SQL injection vulnerability in the addslashes method in SilverStripe 2.3.x before 2.3.12 and 2.4.x before 2.4.6, when connected to a MySQL…
published 2012-09-17 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4866
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
SQL injection vulnerability in the addslashes method in SilverStripe 2.3.x before 2.3.12 and 2.4.x before 2.4.6, when connected to a MySQL database using far east character encodings, allows remote attackers to execute arbitrary SQL commands via unspecified vectors.
Patch / fix
Exploit prediction
1.45% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/silverstripe/sapphire/commit/73cca09 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/silverstripe/silverstripe-cms/commit/b5ea2f6 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/silverstripe/sapphire/commit/ca78784 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/silverstripe/sapphire/commit/73cca09
exploit, patch
-
github.com
/silverstripe/silverstripe-cms/commit/b5ea2f6
exploit, patch
-
github.com
/silverstripe/sapphire/commit/ca78784
exploit, patch
-
doc.silverstripe.org
/framework/en/trunk/changelogs/2.3.12
vendor-advisory
-
doc.silverstripe.org
/framework/en/trunk/changelogs/2.4.6
vendor-advisory
-
openwall.com
/lists/oss-security/2012/04/30/1
mailing-list
-
openwall.com
/lists/oss-security/2012/04/30/3
mailing-list
Sources
- CVE List CVE-2011-4959
- NVD CVE-2011-4959
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.