dbcve.org
Open RedirectWeakness · CWE-601

CVE-2024-56960

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/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
An issue in Tianjin Xiaowu Information technology Co., Ltd BeiKe Holdings iOS 1.3.50 allows attackers to access sensitive user information via supplying a crafted link.

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 · moderate confidence

The BeiKe Holdings iOS app version 1.3.50 contains a vulnerability where attackers can access sensitive user information by providing a crafted link. This appears to involve improper validation of user-supplied links that leads to unauthorized access to sensitive data, likely through an open redirect or link injection flaw.

MitigationImplement proper validation and sanitization of all user-supplied URLs/links, enforce authentication and authorization checks for sensitive data access endpoints, and validate that redirect targets are within trusted domains.

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
None
Availability
None

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

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

  1. Confirm BeiKe Holdings iOS app is installed
    Navigate to the iOS device home screen and locate the BeiKe Holdings app icon. Alternatively, go to Settings > General > iPhone Storage (or Settings > General > iStorage) and scroll to find the app in the list of installed applications.
    Affected if The BeiKe Holdings iOS app is present on the device
  2. Identify the installed app version
    Go to Settings > General > iPhone Storage, tap on the BeiKe Holdings app, and view the version number displayed under the app name. Alternatively, open the App Store, search for BeiKe Holdings, and check the version listed in the app details.
    Affected if The installed version is 1.3.50
  3. Determine if the app processes external links
    Open the BeiKe Holdings app and look for features that accept or display links, such as shared content viewers, message/notification links, web links within the app, or any share sheet integration. Check if the app parses URLs from external sources.
    Affected if The app accepts or processes external URLs or links from untrusted sources
  4. Check for unusual link handling behavior
    Within the app, attempt to access any feature that accepts a URL input or displays linked content. Observe if the app validates the URL domain or allows arbitrary redirect targets. Look for any webviews or content display areas that might accept unsanitized links.
    Affected if The app does not validate that links redirect to trusted domains or allows arbitrary URL manipulation
  5. Inspect network traffic for link-related requests
    If you have access to network logging tools (such as a proxy or network inspection utility), use them to capture traffic while the app processes any external links. Look for requests where the referer or URL parameters contain user-supplied link data being sent to sensitive endpoints.
    Affected if The app sends user-supplied link data to sensitive endpoints without proper validation

A user is affected if the BeiKe Holdings iOS app version 1.3.50 is installed and the app processes or displays external links without validating redirect targets are within trusted domains.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper validation and sanitization of all user-supplied URLs/links, enforce authentication and authorization checks for sensitive data access endpoints, and validate that redirect targets are within trusted domains.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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