CVE-2006-0970
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 · uneditedPHP remote file inclusion vulnerability in index.php in one or more ActiveCampaign products, possibly SupportTrio, allows remote attackers to include and execute arbitrary files via the page parameter.
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 · moderate confidenceRemote file inclusion (RFI) vulnerability in index.php where the 'page' parameter is not properly sanitized, allowing remote attackers to inject arbitrary file URLs that PHP will include and execute server-side.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Activecampaign productSearch the web root for index.php files that contain 'Activecampaign' or the specific product name in comments/headers. Check for directories like /admin/, /supporttrio/, /knowledgebuilder/, /visualedit/, or /isalient/ that indicate which Activecampaign component is present.Affected if Any Activecampaign product (1 2 All, General, Isalient, Knowledgebuilder, Supporttrio, or Visualedit) is found on the server.
-
Locate vulnerable index.phpFind the main index.php file in the Activecampaign installation directory. Search for code that handles the 'page' parameter, typically using $_GET['page'] or similar superglobal without validation.Affected if An index.php file exists that processes a 'page' parameter from user input without sanitization.
-
Check page parameter handlingExamine the index.php source code around the 'page' parameter usage. Look for include(), require(), include_once(), or require_once() statements that use the 'page' parameter directly or with minimal string manipulation (e.g., $page.'.php').Affected if The code uses the 'page' parameter in include/require statements without whitelist validation or proper sanitization.
-
Verify PHP allow_url_include settingCheck php.ini or run phpinfo() to determine if the allow_url_include directive is enabled (set to On). This setting controls whether PHP allows including files from remote URLs.Affected if allow_url_include is enabled, which allows the RFI to execute remote PHP code.
-
Assess network exposureDetermine if the Activecampaign installation is accessible from the internet. Check firewall rules, web server configuration, and routing to see if port 80/443 is exposed externally.Affected if The vulnerable index.php is reachable from untrusted networks, allowing remote attackers to send malicious 'page' parameter values.
A user is affected if any Activecampaign product version is installed with a vulnerable index.php that uses the unsanitized 'page' parameter in include/require statements and the application is network-accessible.
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 dataImplement strict input validation on the page parameter using a whitelist approach, or disable allow_url_include in PHP configuration to prevent remote file inclusions.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2006-0970 — 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-2006-0970 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