CVE-2006-5592
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 · uneditedAdmin/adpoll.asp in PacPoll 4.0 and earlier allows remote attackers to bypass authentication by setting the polllog cookie value to "xx".
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 confidenceThe PacPoll 4.0 admin panel (admin/adpoll.asp) contains an authentication bypass vulnerability where setting the polllog cookie value to 'xx' grants unauthorized administrative access without valid credentials. This is a classic insecure cookie-based authentication flaw where the application trusts client-side cookie values to determine authentication status rather than server-side session validation.
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<= 4.0CVSS 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.
-
Confirm PacPoll installation versionLocate the PacPoll installation directory and identify the installed version through version files, about pages, or application metadata that displays the PacPoll version number.Affected if Installed version is PacPoll 4.0 or lower
-
Check if admin/adpoll.asp existsAttempt to access the path admin/adpoll.asp on the web server through a browser or HTTP request tool.Affected if The file admin/adpoll.asp exists and is accessible via HTTP
-
Test cookie-based authentication bypassSend an HTTP request to admin/adpoll.asp with the polllog cookie set to the value 'xx' and observe whether administrative access is granted without valid credentials.Affected if Setting the polllog cookie to 'xx' grants unauthorized administrative access
-
Review authentication logic in adpoll.aspExamine the source code of admin/adpoll.asp to determine if authentication decisions rely on client-supplied cookie values rather than server-side session validation.Affected if The application trusts cookie values from the client for authorization decisions
Your environment is affected if PacPoll version 4.0 or lower is installed, the admin/adpoll.asp file is accessible, and setting the polllog cookie to 'xx' bypasses normal authentication controls.
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 dataUpgrade PacPoll to a version where authentication is properly enforced through server-side session validation, or implement proper authentication checks in admin/adpoll.asp that do not rely on client-supplied cookie values for authorization decisions.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-5592 — 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-5592 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