Cms Made SimpleApplication · Cmsmadesimple

CVE-2014-2245

MEDIUM · 6.0 CVSS v2.0 Published 2014-03-05
Fix available
A fix is available. Upgrade to after 1.11.9 or later.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
SQL injection vulnerability in the News module in CMS Made Simple (CMSMS) before 1.11.10 allows remote authenticated users with the "Modify News" permission to execute arbitrary SQL commands via the sortby parameter to admin/moduleinterface.php. NOTE: some of these details are obtained from third party information.

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 confidence

SQL injection vulnerability in CMS Made Simple's News module allows authenticated users with 'Modify News' permission to execute arbitrary SQL commands via the sortby parameter in admin/moduleinterface.php.

MitigationUpgrade to CMS Made Simple 1.11.10 or later. Alternatively, implement parameterized queries/prepared statements for the sortby parameter and apply input validation to prevent SQL injection attacks.

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
Cms Made SimpleApplication
Affected:<= 1.11.9= 0.1= 0.2= 0.2.1= 0.3= 0.3.1= 0.3.2= 0.4= 0.4.1= 0.5= 0.5.1= 0.6

CVSS 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
M
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:S/C:P/I:P/A:P

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify CMS Made Simple version
    Check the version number displayed in the CMS admin dashboard footer or in the file includes/version.php
    Affected if The installed version is 1.11.9 or lower, or falls within 0.1 to 0.6.x range
  2. Verify News module is installed
    Log in to the CMS admin panel and navigate to the News module section, or check for the News module in the module management area
    Affected if The News module is installed and accessible in the admin interface
  3. Confirm user permission level
    Check the user account permissions in the admin panel under User Manager to verify if the account has 'Modify News' permission
    Affected if The logged-in user has 'Modify News' permission granted
  4. Inspect the vulnerable parameter handling
    Examine the file admin/moduleinterface.php in the News module directory for unsanitized use of the sortby parameter in SQL queries
    Affected if The sortby parameter is used directly in SQL queries without parameterized preparation or input validation

You are affected if your CMS Made Simple version is 1.11.9 or lower (or 0.1-0.6.x), the News module is installed, and the sortby parameter in the News module's admin interface handles SQL queries without proper sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.11.9
Interim mitigation

Upgrade to CMS Made Simple 1.11.10 or later. Alternatively, implement parameterized queries/prepared statements for the sortby parameter and apply input validation to prevent SQL injection attacks.

Fix this in Cms Made Simple Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-2245 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-2245 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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