# CVE-2025-25060: Missing authorization in AssetView

> Remote unauthenticated attackers can read or delete server files due to missing authentication in AssetView and AssetView CLOUD.

- **Severity:** High 8.2 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2025
- **Updated:** 2 Apr 2025
- **Also known as:** GHSA-rh42-r2fh-w434

## What is CVE-2025-25060?

CVE-2025-25060 is a high-severity missing authorization vulnerability in Hammock Corporation AssetView, published on 2 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing authentication for critical function vulnerability exists in AssetView and AssetView CLOUD. If exploited, the files on the server where the product is running may be obtained and/or deleted by a remote unauthenticated attacker.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-25060?


## How do I fix CVE-2025-25060?

No fix has been published for CVE-2025-25060 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-25060 being exploited?

There is no known exploitation of CVE-2025-25060 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-25060 and fix it if it is affected.

What it is: CVE-2025-25060 is a high-severity missing authorization vulnerability in Hammock Corporation AssetView, published on 2 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-25060 in the wild and no public exploit code.

Affected product: Hammock Corporation AssetView. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-25060/ (Markdown: https://insights.sbomify.com/CVE-2025-25060/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-25060
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-25060
- OSV: https://osv.dev/vulnerability/CVE-2025-25060

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-25060/
Summaries are generated and may contain mistakes; the official description above is the record.