Commonspot Content ServerApplication · Paperthin

CVE-2014-2868

HIGH · 7.5 CVSS v2.0 Published 2014-04-15
Fix available
A fix is available. Upgrade to after 7.0.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
PaperThin CommonSpot before 7.0.2 and 8.x before 8.0.3 allows remote attackers to modify the flow of execution of ColdFusion code by using an HTTP GET request to set a ColdFusion variable.

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

PaperThin CommonSpot CMS before 7.0.2 and 8.x before 8.0.3 contains a parameter injection vulnerability where HTTP GET request parameters can directly set ColdFusion variables, allowing remote attackers to manipulate application execution flow. This stems from insufficient sanitization of user-supplied input being used to populate server-side variables.

MitigationUpgrade to CommonSpot 7.0.2 or 8.0.3 or later, or implement input validation/sanitization to prevent arbitrary GET parameters from setting ColdFusion variables. If immediate upgrade is not feasible, deploy a WAF rule to block suspicious parameter manipulation attempts.

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
Commonspot Content ServerApplication
Affected:<= 7.0.1= 8.0.0= 8.0.1= 8.0.2

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
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/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 installed CommonSpot version
    Check the version file or admin interface: Look for version.info, about.cfm in the CommonSpot administration directory, or log into the CommonSpot Admin Dashboard to view the version information under the Help or About section
    Affected if The installed version is 7.0.1 or earlier, or 8.0.0 through 8.0.2
  2. Locate ColdFusion entry point scripts
    Identify the main CommonSpot entry points - typically index.cfm, url.cfm, or any.cfm in the site root or /commonspot/ directory - these handle incoming HTTP requests
    Affected if These entry scripts exist and process incoming request parameters
  3. Inspect parameter handling code
    Review the ColdFusion code at the entry points (index.cfm, url.cfm, any.cfm) for direct usage of URL or Form scope variables without sanitization - look for patterns like #url.variableName# or #form.variableName# being used directly in application logic or database queries
    Affected if The code directly uses URL or Form scope parameters (e.g., #url.paramName#) in application logic without input validation functions like HTMLEditFormat() or EncodeForHTML()
  4. Test for parameter injection (if authorized)
    With explicit authorization, send a test GET request with an arbitrary parameter such as ?testparam=injectedvalue and check if the application reflects or uses this parameter value in a way that demonstrates it sets ColdFusion variables directly (e.g., checking response for the injected value or observing behavior changes)
    Affected if The application accepts and acts upon arbitrary GET parameters without sanitization, allowing them to influence server-side variable values

You are affected if your installed CommonSpot version is 7.0.1 or earlier, or 8.0.0-8.0.2, AND the application processes GET parameters in an unsafe manner that allows them to set ColdFusion variables directly.

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 7.0.1
Interim mitigation

Upgrade to CommonSpot 7.0.2 or 8.0.3 or later, or implement input validation/sanitization to prevent arbitrary GET parameters from setting ColdFusion variables. If immediate upgrade is not feasible, deploy a WAF rule to block suspicious parameter manipulation attempts.

Fix this in Commonspot Content Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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