CVE-2006-1488
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 · uneditedActiveCampaign SupportTrio 2.5 allows remote attackers to obtain the full path of the server via invalid (1) article or (2) print parameters in a kb action to index.php, or (3) an invalid category parameter to modules/KB/pdf.php, which leaks the path in an error message.
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 confidenceActiveCampaign SupportTrio 2.5 contains a path disclosure vulnerability where invalid parameters to index.php (article or print parameters in a kb action) and modules/KB/pdf.php (category parameter) cause error messages that reveal the full server filesystem path. This information can aid attackers in further reconnaissance and exploitation.
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.50.2CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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.
-
Locate SupportTrio installationSearch for the SupportTrio installation directory on your web server. Common paths include /supporttrio, /support, or under web root. Look for directories containing index.php and modules/KB/.Affected if The SupportTrio application is not found on the server.
-
Verify the application versionCheck for version information in the SupportTrio files. Look for version strings in index.php, about.php, or a VERSION file within the installation directory. Compare your version to 2.50.2.Affected if The installed version is exactly 2.50.2.
-
Test index.php for path disclosure via article parameterMake an HTTP request to index.php with the kb action and an invalid article parameter. Example: /supporttrio/index.php?action=kb&article=INVALID999. Check if the response contains the full server filesystem path in error messages.Affected if Error messages display absolute server paths such as /home/user/public_html/supporttrio/.
-
Test index.php for path disclosure via print parameterMake an HTTP request to index.php with the kb action and an invalid print parameter. Example: /supporttrio/index.php?action=kb&print=INVALID999. Examine the response for full filesystem paths in any error output.Affected if Error messages reveal the full server path to the application directory.
-
Test modules/KB/pdf.php for path disclosure via category parameterMake an HTTP request to modules/KB/pdf.php with an invalid category parameter. Example: /supporttrio/modules/KB/pdf.php?category=INVALID999. Inspect the response for path disclosure in error messages.Affected if Error messages expose the server filesystem path.
If SupportTrio version 2.50.2 is installed and any of the tested endpoints (index.php with kb action or modules/KB/pdf.php) return error messages showing the full server filesystem path when given invalid parameters, the environment is affected by CVE-2006-1488.
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 proper error handling and input validation to suppress detailed error messages in production environments, or upgrade to a patched version if available.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-1488 — 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-1488 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