CVE-2019-9060
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 · uneditedAn issue was discovered in CMS Made Simple 2.2.8. It is possible to achieve unauthenticated path traversal in the CGExtensions module (in the file action.setdefaulttemplate.php) with the m1_filename parameter; and through the action.showmessage.php file, it is possible to read arbitrary file content (by using that path traversal with m1_prefname set to cg_errormsg and m1_resettodefault=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 confidenceUnauthenticated path traversal vulnerability in CMS Made Simple 2.2.8's CGExtensions module allows attackers to read arbitrary files on the server. The first attack vector uses the m1_filename parameter in action.setdefaulttemplate.php, while the second uses m1_prefname=cg_errormsg with m1_resettodefault=1 in action.showmessage.php to access sensitive files.
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.8CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 installation versionLocate the version file or check the admin dashboard for the installed CMS Made Simple version numberAffected if The installed version is exactly 2.2.8
-
Check if CGExtensions module is installedList the installed modules in the CMS Made Simple admin panel or inspect the modules directory for CGExtensionsAffected if The CGExtensions module is present and enabled on the system
-
Verify vulnerable endpoint availabilityCheck for the presence of action.setdefaulttemplate.php and action.showmessage.php files within the CGExtensions module directoryAffected if Both files exist in the CGExtensions module path
-
Confirm module is accessible without authenticationAttempt to access the CGExtensions module endpoints directly without logging in to verify if the module is publicly accessibleAffected if The endpoints are reachable without authentication
-
Inspect for path traversal in module parametersReview the CGExtensions module configuration or logs for usage of m1_filename, m1_prefname, or m1_resettodefault parametersAffected if These parameters are accepted and processed by the module
A system is affected if it runs CMS Made Simple version 2.2.8 with the CGExtensions module installed and enabled, allowing unauthenticated access to the vulnerable PHP files.
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 dataUpdate CMS Made Simple and the CGExtensions module to patched versions, or disable the CGExtensions module if not required. Consider implementing web application firewall rules to block path traversal patterns in URL parameters.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9060 — 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-2019-9060 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