dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-5247

HIGH · 7.3 CVSS v3.1 Published 2025-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
A vulnerability, which was classified as critical, has been found in Gowabby HFish 0.1. This issue affects the function LoadUrl of the file \view\url.go. The manipulation of the argument r leads to improper authentication. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

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

A critical authentication bypass vulnerability exists in Gowabby HFish 0.1's LoadUrl function in view/url.go. The function fails to properly validate the authentication state when processing the 'r' argument, allowing remote attackers to bypass authentication controls and access protected URL/view functionality without valid credentials.

MitigationFix the LoadUrl function in view/url.go to enforce proper authentication checks before processing requests. Review similar functions in the codebase for related authentication issues. Given the public exploit disclosure, prioritize rapid remediation and assume active exploitation.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 HFish installation and version
    Locate the HFish installation directory and check the version file or binary version. Common paths include /opt/hfish, /usr/local/hfish, or the installation root directory. Look for version markers such as a VERSION file, version in binary output (e.g., hfish version), or in configuration files.
    Affected if The installed version is HFish 0.1 or the specific version cannot be determined but matches the vulnerable release.
  2. Locate and inspect view/url.go
    Navigate to the view/ directory in the HFish installation root and verify the presence of url.go. Examine the LoadUrl function within this file, specifically looking for how the 'r' argument is processed and whether authentication validation occurs before processing the request.
    Affected if The file view/url.go exists and contains a LoadUrl function that processes the 'r' parameter without performing authentication state validation.
  3. Verify authentication check implementation
    Search the LoadUrl function code for authentication-related function calls such as IsLogin, CheckAuth, Session validation, or similar authentication verification logic. Examine whether these checks occur before or after the 'r' parameter is processed.
    Affected if The LoadUrl function processes the 'r' argument without calling authentication verification functions, or such checks are missing entirely from the function.
  4. Check exposure of the vulnerable endpoint
    Identify how the LoadUrl function is exposed via HTTP routes. Review the routing configuration (often in main.go or router.go) to determine if this function is accessible via web requests without requiring authentication.
    Affected if The LoadUrl function is mapped to a web route that does not enforce authentication middleware, making it externally accessible.

If HFish version 0.1 is installed with the view/url.go file containing a LoadUrl function that processes the 'r' parameter without proper authentication validation and this endpoint is exposed without auth middleware, the environment is affected by CVE-2025-5247.

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

Fix the LoadUrl function in view/url.go to enforce proper authentication checks before processing requests. Review similar functions in the codebase for related authentication issues. Given the public exploit disclosure, prioritize rapid remediation and assume active exploitation.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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