CVE-2026-32616
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 · uneditedPigeon is a message board/notepad/social system/blog. Prior to 1.0.201, the application uses $_SERVER['HTTP_HOST'] without validation to construct email verification URLs in the register and resendmail flows. An attacker can manipulate the Host header in the HTTP request, causing the verification link sent to the user's email to point to an attacker-controlled domain. This can lead to account takeover by stealing the email verification token. This vulnerability is fixed in 1.0.201.
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 Pigeon application uses $_SERVER['HTTP_HOST'] directly without validation to construct email verification URLs in the register and resendmail flows. An attacker can manipulate the HTTP Host header to inject an attacker-controlled domain into verification links, allowing them to intercept verification tokens and achieve account takeover.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/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.
-
Identify Pigeon application installationSearch for files named 'pigeon.php' or directories containing 'Pigeon' in your web root, or check your application framework's base directory for the Pigeon application codeAffected if Pigeon application is present on the server
-
Check Pigeon versionLocate the main Pigeon application file (typically index.php, config.php, or a VERSION file) and read the defined version constant or variableAffected if The installed version is earlier than 1.201
-
Examine register flow code for HTTP_HOST usageSearch the codebase for files handling registration (commonly 'register.php', 'RegisterController.php', or similar) and inspect lines using $_SERVER['HTTP_HOST'] without sanitizationAffected if $_SERVER['HTTP_HOST'] is used directly in URL construction without validation or allowlist checks
-
Examine resendmail flow code for HTTP_HOST usageSearch the codebase for files handling email resend (commonly 'resendmail.php', 'ResendController.php', or similar) and inspect lines using $_SERVER['HTTP_HOST'] without sanitizationAffected if $_SERVER['HTTP_HOST'] is used directly in URL construction without validation or allowlist checks
-
Verify Host header validation existsSearch the application for HTTP_HOST validation logic using keywords like 'allowed_hosts', 'valid_host', 'whitelist', or 'filter_var' with FILTER_VALIDATE_URLAffected if No validation or allowlist logic is found for HTTP_HOST before constructing URLs
A system is affected if the Pigeon version is below 1.201 AND the register or resendmail flows use $_SERVER['HTTP_HOST'] directly in URL construction without any validation or allowlist filtering.
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.
dbcve · scopedUpgrade to version 1.201 or later. Alternatively, implement strict validation of the HTTP_HOST header against an allowlist of trusted domains before using it in URL construction.
1.0.201
- 1. Identify the currently running Pigeon version by checking the application configuration or version file
- 2. Backup the current application database and files before performing the upgrade
- 3. Download Pigeon version 1.0.201 from the official GitHub repository
- 4. Replace the existing application files with the new version 1.0.201 files
- 5. Verify that the application correctly validates the Host header in email verification URLs by testing the register and resendmail flows
- 6. Confirm that email verification links now use a validated, trusted domain rather than the attacker-controlled Host header value
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32616 — 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-2026-32616 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