ClearsiteApplication · Richrumble

CVE-2010-2145

HIGH · 7.5 CVSS v2.0 Published 2010-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Multiple PHP remote file inclusion vulnerabilities in ClearSite Beta 4.50, and possibly other versions, allow remote attackers to execute arbitrary PHP code via a URL in the cs_base_path parameter to (1) docs.php and (2) include/admin/device_admin.php. NOTE: the header.php vector is already covered by CVE-2009-3306. NOTE: this issue may be due to a variable extraction error.

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

Remote File Inclusion (RFI) vulnerability in ClearSite Beta 4.50 allows remote attackers to execute arbitrary PHP code by supplying a malicious URL in the cs_base_path parameter to docs.php and include/admin/device_admin.php. The vulnerability stems from a variable extraction error that allows user-controlled input to be used in include/require statements without proper validation.

MitigationImmediately remove or restrict access to vulnerable files (docs.php, include/admin/device_admin.php). If the application is still needed, apply vendor patches or upgrade to a patched version. Implement strict input validation on the cs_base_path parameter to prevent URL-based file inclusion.

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
ClearsiteApplication
Affected:= 4.50

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. Confirm ClearSite installation and version
    Locate the ClearSite installation directory and check for version information in the application's main files, configuration, or an about page. Typical locations include the web root or documentation files.
    Affected if The installed version is ClearSite Beta 4.50
  2. Identify vulnerable files
    Check for the presence of docs.php and include/admin/device_admin.php in the web application directory structure.
    Affected if Either docs.php or include/admin/device_admin.php exists in the application
  3. Verify cs_base_path parameter handling
    Review the source code of docs.php and include/admin/device_admin.php to confirm that the cs_base_path parameter is used in include or require statements without proper validation.
    Affected if The cs_base_path parameter is directly used in include/require statements without sanitization
  4. Check PHP allow_url_include setting
    Inspect the PHP configuration file (php.ini) or run phpinfo() to check the value of allow_url_include.
    Affected if allow_url_include is enabled (set to On), which permits including remote files
  5. Test RFI vulnerability
    Send an HTTP request to docs.php or include/admin/device_admin.php with cs_base_path pointing to an external URL containing PHP code, observing if the remote code is executed.
    Affected if The application executes code from a remote URL supplied in the cs_base_path parameter

A system is affected if it runs ClearSite Beta 4.50 with the vulnerable files present and the cs_base_path parameter accessible to external attackers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately remove or restrict access to vulnerable files (docs.php, include/admin/device_admin.php). If the application is still needed, apply vendor patches or upgrade to a patched version. Implement strict input validation on the cs_base_path parameter to prevent URL-based file inclusion.

Fix this in Clearsite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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