dbcve.org
Open RedirectWeakness · CWE-601

CVE-2024-53264

MEDIUM · 5.1 CVSS v4.0 Published 2024-11-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
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
bunkerweb is an Open-source and next-generation Web Application Firewall (WAF). A open redirect vulnerability exists in the loading endpoint, allowing attackers to redirect authenticated users to arbitrary external URLs via the "next" parameter. The loading endpoint accepts and uses an unvalidated "next" parameter for redirects. Ex. visiting: `/loading?next=https://google.com` while authenticated will cause the page will redirect to google.com. This vulnerability could be used in phishing attacks by redirecting users from a legitimate application URL to malicious sites. This issue has been addressed in version 1.5.11. Users are advised to upgrade. There are no known workarounds for this vulnerability.

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

Open redirect vulnerability in bunkerweb's loading endpoint where the 'next' parameter is not validated before use in redirects. Authenticated users visiting /loading?next=https://evil.com are redirected to arbitrary external URLs, enabling phishing attacks.

MitigationUpgrade to bunkerweb version 1.5.11 or later to address this vulnerability, as no workarounds are available.

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
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 bunkerweb installation
    Locate bunkerweb installation by checking for running bunkerweb processes (ps aux | grep bunkerweb) or container status (docker ps). Check common installation paths like /etc/bunkerweb or look for bunkerweb configuration files.
    Affected if bunkerweb is not installed or not running - no vulnerability present
  2. Determine installed bunkerweb version
    Run the command to check the bunkerweb version: 'bunkerweb version' if CLI available, or check the Docker image tag (docker images), or inspect the installed package version (apt list --installed 2>/dev/null | grep bunkerweb).
    Affected if version is unknown or is below 1.5.11 - vulnerability may be present
  3. Verify /loading endpoint accessibility
    Check if the /loading endpoint is accessible by attempting to access http://[host]/loading or reviewing bunkerweb configuration files for route definitions that expose /loading to authenticated users.
    Affected if the /loading endpoint is exposed and accessible to authenticated users - vulnerability can be exploited
  4. Test next parameter for open redirect behavior
    As an authenticated user, attempt to access /loading?next=https://example.com and verify if the application redirects to the URL specified in the next parameter without proper validation.
    Affected if the application redirects to arbitrary URLs in the next parameter without validation - vulnerability is confirmed

User is affected if bunkerweb is installed with a version below 1.5.11 and the /loading endpoint with the unauthenticated next parameter is accessible to authenticated users.

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 bunkerweb version 1.5.11 or later to address this vulnerability, as no workarounds are available.

Recommended fix High confidence

1.5.11

  1. Backup your current bunkerweb configuration and data
  2. Stop the bunkerweb service
  3. Upgrade bunkerweb to version 1.5.11 or later
  4. Verify the upgrade was successful by checking the installed version
  5. Start the bunkerweb service
  6. Test that the vulnerability is fixed by visiting /loading?next=https://google.com while authenticated - it should no longer redirect to external URLs

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Check whether your project pulls in CVE-2024-53264 — 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-2024-53264 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