dbcve.org
Open RedirectWeakness · CWE-601

CVE-2026-40905

HIGH · 8.1 CVSS v3.1 Published 2026-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
LinkAce is a self-hosted archive to collect website links. Prior to 2.5.4, a password reset poisoning vulnerability was identified in the application due to improper trust of user-controlled HTTP headers. The application uses the X-Forwarded-Host header when generating password reset URLs. By manipulating this header during a password reset request, an attacker can inject an attacker-controlled domain into the reset link sent via email. As a result, the victim receives a password reset email containing a malicious link pointing to an attacker-controlled domain. When the victim clicks the link, the password reset token is transmitted to the attacker-controlled server. An attacker can capture this token and use it to reset the victim’s password, leading to full account takeover. This vulnerability is fixed in 2.5.4.

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 confidence

LinkAce versions prior to 2.5.4 suffer from a password reset poisoning vulnerability where the application improperly trusts the X-Forwarded-Host header when generating password reset URLs. Attackers can manipulate this header to inject an attacker-controlled domain into the reset link sent via email, allowing them to capture the reset token and take over victim accounts.

MitigationUpgrade to LinkAce version 2.5.4 or later. As a temporary measure, configure the application to not trust X-Forwarded-Host headers for password reset URL generation by using a fixed, trusted domain or implementing strict host header validation.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify LinkAce version
    Locate the version file or check the admin dashboard for the installed LinkAce version number
    Affected if The installed version is prior to 2.5.4 (e.g., 2.5.3, 2.5.0, 2.4.x)
  2. Verify password reset functionality is enabled
    Confirm that password reset via email is active in the application settings or that the /password/reset route is accessible
    Affected if Password reset emails can be triggered and the application generates reset URLs internally
  3. Inspect host header configuration
    Examine the application configuration files or environment settings for any directive that controls X-Forwarded-Host header handling (e.g., TRUSTED_HOSTS, ALLOWED_HOSTS, or similar settings)
    Affected if The application is configured to trust or use the X-Forwarded-Host header for constructing URLs, especially for password reset links
  4. Check if application sits behind a reverse proxy
    Determine whether the web server or application is running behind a proxy that forwards X-Forwarded-Host headers without additional validation
    Affected if The application receives and processes X-Forwarded-Host headers from upstream proxies without strict validation against an allowlist

A user is affected if their LinkAce installation is version 2.5.3 or earlier AND the application trusts the X-Forwarded-Host header when generating password reset URLs, allowing attackers to inject malicious domains into reset links.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to LinkAce version 2.5.4 or later. As a temporary measure, configure the application to not trust X-Forwarded-Host headers for password reset URL generation by using a fixed, trusted domain or implementing strict host header validation.

Recommended fix High confidence

2.5.4

  1. Backup the existing LinkAce installation and database before starting the upgrade
  2. Download LinkAce version 2.5.4 from the official GitHub repository
  3. Replace the existing LinkAce files with the new version 2.5.4 files
  4. Run any database migrations if included in the release (check for migrate script or artisan commands)
  5. Verify the application is functioning correctly after the upgrade
  6. Confirm the X-Forwarded-Host header is no longer trusted for password reset URL generation

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40905 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40905 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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