dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-7355

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Authorization Bypass Through User-Controlled Key vulnerability in Beefull Energy Technologies Beefull App allows Exploitation of Trusted Identifiers. This issue affects Beefull App: before 24.07.2025.

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 vulnerability is an Authorization Bypass Through User-Controlled Key (IDOR-like), where the Beefull App accepts user-supplied identifiers (likely object IDs, record IDs, or resource references) without proper authorization validation. Attackers can manipulate these trusted identifiers to access resources belonging to other users or elevate privileges within the application.

MitigationUpgrade Beefull App to version 24.07.2025 or later. Additionally, implement server-side authorization checks that validate the current user has permission to access the requested resource, regardless of any identifier supplied in the request.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Check installed Beefull App version
    Locate the application version information in the installation directory, configuration file, or by querying the application's about/info endpoint. Common locations include version manifest files, the application's login page source, or API endpoints like /api/version or /health.
    Affected if The installed version is earlier than 24.07.2025 (for example, 24.06.2025, 24.05.x, or any version from 2024).
  2. Identify API endpoints accepting user-controlled identifiers
    Review API documentation, capture network traffic during application use, or examine application routing configuration. Look for endpoints that accept object IDs, record IDs, file references, or resource identifiers as URL parameters, query strings, or request body fields.
    Affected if The application exposes endpoints that accept numeric or GUID-based identifiers (such as /api/records/{id}, /api/users/{id}, or similar patterns) without requiring path-based authorization validation.
  3. Test for missing authorization on resource access
    Using an authenticated user account, access a resource belonging to another user by manipulating identifier values in API requests. Compare the HTTP response codes and returned data when accessing resources with IDs that should belong to different users.
    Affected if Requests with valid authentication but manipulated identifiers (not belonging to the current user) return successful responses (HTTP 200) instead of being rejected with HTTP 403 or 404.
  4. Review application logs for unauthorized access attempts
    Examine application audit logs, access logs, or security event logs for patterns where resource identifiers do not match the authenticated user's expected permissions. Look for repeated access to diverse resource IDs from the same session.
    Affected if Logs show access patterns where users are accessing resource IDs outside their expected scope, or authorization failures are not being enforced.

You are affected if the Beefull App version is earlier than 24.07.2025 AND the application exposes API endpoints that accept user-supplied identifiers without proper ownership/permission validation on each request.

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

Upgrade Beefull App to version 24.07.2025 or later. Additionally, implement server-side authorization checks that validate the current user has permission to access the requested resource, regardless of any identifier supplied in the request.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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