dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-7115

HIGH · 7.3 CVSS v3.1 Published 2025-07-07
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 was found in rowboatlabs rowboat up to 8096eaf63b5a0732edd8f812bee05b78e214ee97. It has been rated as critical. Affected by this issue is the function PUT of the file apps/rowboat/app/api/uploads/[fileId]/route.ts of the component Session Handler. The manipulation of the argument params leads to missing authentication. The attack may be launched remotely. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. It is expected that this issue will be fixed in the near future.

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 rowboat application has a missing authentication vulnerability in the PUT method of the file upload API endpoint at apps/rowboat/app/api/uploads/[fileId]/route.ts. This allows unauthenticated remote attackers to upload or modify files through the Session Handler component by manipulating the params argument.

MitigationImplement authentication and authorization checks on the PUT endpoint to verify user identity before allowing file uploads. Validate that the authenticated user has permission to modify the specific file identified in the request parameters.

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. Confirm rowboat application installation
    Search for the rowboat application directory or package in your environment. Look for directories named 'rowboat' or check package.json files for rowboat dependencies.
    Affected if Rowboat application is present in your environment and exposes the vulnerable API endpoint.
  2. Locate the vulnerable API route file
    Find the file at apps/rowboat/app/api/uploads/[fileId]/route.ts in your rowboat installation directory. This is the exact path referenced in the CVE.
    Affected if The file exists and contains a PUT method handler for file uploads.
  3. Inspect PUT method for authentication
    Open the route.ts file and examine the PUT method implementation. Look for authentication middleware, session validation, or authorization checks before file upload logic.
    Affected if The PUT method lacks authentication or authorization checks and directly processes file upload requests.
  4. Check Session Handler component configuration
    Locate and examine the Session Handler component that processes the params argument used in the upload endpoint. Look for how session data is validated (or not validated) when handling file upload requests.
    Affected if The Session Handler accepts and processes requests without validating user identity and does not verify permissions for the file identified in request parameters.
  5. Verify endpoint is network-accessible
    Test if the /api/uploads/[fileId] endpoint responds to PUT requests from an unauthenticated source. Attempt a PUT request without providing authentication credentials.
    Affected if The endpoint accepts and processes PUT requests without requiring valid authentication tokens or session cookies.

You are affected if the rowboat application is installed and the PUT method in apps/rowboat/app/api/uploads/[fileId]/route.ts processes file upload requests without validating user authentication or authorization through the Session Handler component.

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

Implement authentication and authorization checks on the PUT endpoint to verify user identity before allowing file uploads. Validate that the authenticated user has permission to modify the specific file identified in the request parameters.

Recommended fix Moderate confidence
  1. Locate the vulnerable file at apps/rowboat/app/api/uploads/[fileId]/route.ts
  2. Examine the existing PUT handler function in this file
  3. Add authentication middleware or check at the beginning of the PUT function to verify the user is authenticated
  4. Common approaches include: importing an auth utility (e.g., getCurrentUser, verifySession) and returning 401 Unauthorized if no valid session exists, or wrapping the handler with an auth higher-order function
  5. Ensure the authentication check validates the session token or credentials before allowing any file upload operations
  6. Test the fix by attempting an unauthenticated PUT request to confirm it returns 401/403
  7. If the project uses a framework like NextAuth.js, add session verification: const session = await getServerSession(authOptions); if (!session) return NextResponse.json({error: 'Unauthorized'}, {status: 401})

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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