CVE-2017-1000454
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCMS Made Simple 2.1.6, 2.2, 2.2.1 are vulnerable to Smarty Template Injection in some core components, resulting in local file read before 2.2, and local file inclusion since 2.2.1
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCMS Made Simple versions 2.1.6 through 2.2.1 contain a Smarty Template Injection vulnerability in core components that allows unauthenticated attackers to inject malicious Smarty code. In versions before 2.2, this enables local file read; in version 2.2.1 and later, it escalates to local file inclusion, potentially allowing remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.2>= 2.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify CMS Made Simple installationLook for CMS Made Simple in the web application's directory structure, typically in the root web folder. Check for the file 'lib/classes/class.CMSModule.php' or search for 'cmsms' in configuration files.Affected if CMS Made Simple is not present on the system
-
Determine installed CMS Made Simple versionCheck the version file typically located at 'lib/version.php' or 'doc/info.xml' in the CMS Made Simple installation directory. Open the file and locate the version number.Affected if The installed version cannot be determined or the file does not exist
-
Compare version against affected rangeReview the version number obtained from step 2. Compare it against the affected ranges: version 2.1.6 through version 2.2.0, or version 2.2.1 and later.Affected if The installed version falls within 2.1.6 to 2.2.0 inclusive, or is 2.2.1 or higher (the >= 2.2.1 notation indicates this version and later are affected)
-
Verify Smarty template engine is in useCheck for the presence of the Smarty library in the installation, typically found under 'lib/smarty/' or 'vendor/smarty/' directory. Also verify the application uses Smarty templates by looking for .tpl files in the 'templates/' or 'themes/' directories.Affected if Smarty template engine is not used by the CMS installation
A system is affected if CMS Made Simple is installed with a version between 2.1.6 and 2.2.0 inclusive, or version 2.2.1 or higher, and the application uses Smarty templates.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.2
Upgrade CMS Made Simple to the latest patched version to address the template injection vulnerability. Additionally, disable or restrict Smarty template compilation in production environments as a defense-in-depth measure.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000454 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-1000454 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data