CVE-2011-1513 e107 e107: OS Command Injection
e107 e107: no CVSS score yet. EPSS 5.6% estimated probability of exploitation activity in the next 30 days.
On this page
Static code injection vulnerability in install_.php in e107 CMS 0.7.24 and probably earlier versions, when the installation script is not removed, allows remote attackers to inject arbitrary PHP code into e107_config.php via a crafted MySQL server name.
- EPSS
- 5.6% (unchanged from 5.6% a week ago; 5.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 93rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-78 Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)
- OWASP Top 10
- A05:2025 Injection
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Patch: http://e107.svn.sourceforge.net/viewvc/e107/trunk/e107_0.8/install_.php?r1=11931&r2=12376&pathrev=12376
- Patch: http://www.coresecurity.com/content/e107-cms-script-command-injection
Ask an AI about this CVE
Show the prompt
Explain CVE-2011-1513 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2011-1513?via=ask-ai-copy and https://cve.bz/cve/CVE-2011-1513?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2011-1513 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| e107:e107 | through 0.7.24 |
| e107:e107 | 0.7 |
| e107:e107 | 0.7.0 |
| e107:e107 | 0.7.1 |
| e107:e107 | 0.7.2 |
| e107:e107 | 0.7.3 |
| e107:e107 | 0.7.4 |
| e107:e107 | 0.7.5 |
| e107:e107 | 0.7.6 |
| e107:e107 | 0.7.7 |
| e107:e107 | 0.7.8 |
| e107:e107 | 0.7.9 |
| e107:e107 | 0.7.10 |
| e107:e107 | 0.7.11 |
| e107:e107 | 0.7.12 |
| e107:e107 | 0.7.13 |
| e107:e107 | 0.7.14 |
| e107:e107 | 0.7.15 |
| e107:e107 | 0.7.16 |
| e107:e107 | 0.7.17 |
| e107:e107 | 0.7.18 |
| e107:e107 | 0.7.19 |
| e107:e107 | 0.7.20 |
| e107:e107 | 0.7.21 |
| e107:e107 | 0.7.22 |
| e107:e107 | 0.545 |
| e107:e107 | 0.547:beta |
| e107:e107 | 0.548:beta |
| e107:e107 | 0.549:beta |
| e107:e107 | 0.551:beta |
| e107:e107 | 0.552:beta |
| e107:e107 | 0.553:beta |
| e107:e107 | 0.554 |
| e107:e107 | 0.554:beta |
| e107:e107 | 0.555:beta |
| e107:e107 | 0.600 |
| e107:e107 | 0.601 |
| e107:e107 | 0.602 |
| e107:e107 | 0.603 |
| e107:e107 | 0.604 |
| e107:e107 | 0.605 |
| e107:e107 | 0.606 |
| e107:e107 | 0.607 |
| e107:e107 | 0.608 |
| e107:e107 | 0.609 |
| e107:e107 | 0.610 |
| e107:e107 | 0.611 |
| e107:e107 | 0.612 |
| e107:e107 | 0.613 |
| e107:e107 | 0.614 |
| e107:e107 | 0.615 |
| e107:e107 | 0.615a |
| e107:e107 | 0.616 |
| e107:e107 | 0.617 |
| e107:e107 | 0.6171 |
| e107:e107 | 0.6172 |
| e107:e107 | 0.6173 |
| e107:e107 | 0.6174 |
| e107:e107 | 0.6175 |
Public exploits
- Exploit-DB e107 0.7.24 - 'cmd' Remote Command Execution
Attack patterns (CAPEC)
- CAPEC-6 Argument Injection Likelihood: High · Severity: High
- CAPEC-15 Command Delimiters Likelihood: High · Severity: High
- CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
- CAPEC-88 OS Command Injection Likelihood: High · Severity: High
- CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.