CVE-2006-2422
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 · uneditedphpCOIN 1.2.3 and earlier stores messages based upon e-mail addresses, which allows remote authenticated users to read messages for other users by adding the sender's e-mail address as an "additional contact".
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 confidencephpCOIN 1.2.3 and earlier stores messages by associating them with email addresses rather than properly enforcing user account boundaries. Authenticated users can add another user's email address as an 'additional contact', which allows them to access messages sent to that email address. This is an Insecure Direct Object Reference (IDOR) vulnerability combined with improper access control logic.
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= 1.2= 1.2.1= 1.2.1b= 1.2.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.
-
Confirm phpCOIN installationLook for phpCOIN files in the web root, typically in directories such as /coin, /phpcoin, or the root itself. Check for common phpCOIN files like index.php, config.php, or version.php.Affected if phpCOIN is found on the system
-
Identify phpCOIN versionCheck the version.php file or any version information file in the phpCOIN installation directory. Alternatively, look for version strings in source files such as index.php or config.php.Affected if Version is 1.2.3 or earlier, or falls within 1.2, 1.2.1, 1.2.1b, or 1.2.2
-
Verify multi-user configurationCheck the database or user configuration to determine if more than one user account exists. Look in the users table or user configuration files.Affected if Multiple user accounts are configured in the system
-
Check contact addition featureExamine the contact management functionality in the phpCOIN application. Determine if authenticated users can add additional email contacts to their profile through the admin or user interface.Affected if The additional contact feature is enabled and accessible to authenticated users
-
Inspect message access controlsReview the code handling message retrieval, specifically how messages are associated with users versus email addresses. Check if the system properly validates that a user can only access their own messages.Affected if Messages are associated primarily by email address rather than by validated user account, or no ownership validation exists on message retrieval
A user is affected if phpCOIN version 1.2.3 or earlier (specifically 1.2 through 1.2.2) is installed with multiple user accounts and the additional contact feature is enabled, allowing any authenticated user to add another user's email as a contact and access that user's messages.
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 to a patched version of phpCOIN, or implement proper access controls ensuring users can only retrieve messages associated with their authenticated account regardless of contact configurations. Restrict the ability to add contacts to prevent cross-user message access.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-2422 — 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-2422 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