# CVE-2023-24060: Server-side request forgery in n/a

> Authenticated users can exploit SSRF in Haven's RSS feed functionality to access internal resources or the server itself.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2023
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-jmj5-q6wr-x9v2

## What is CVE-2023-24060?

CVE-2023-24060 is a medium-severity server-side request forgery vulnerability in n/a, published on 27 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Haven 5d15944 allows Server-Side Request Forgery (SSRF) via the feed[url]= Feeds functionality. Authenticated users with the ability to create new RSS Feeds or add RSS Feeds can supply an arbitrary hostname (or even the hostname of the Haven server itself). NOTE: this product has significant usage but does not have numbered releases; ordinary end users may typically use the master branch.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2023-24060?

It affects 1 product.


Products: Havenweb Haven.

## How do I fix CVE-2023-24060?

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

## Is CVE-2023-24060 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24060 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-24060 and fix it if it is affected.

What it is: CVE-2023-24060 is a medium-severity server-side request forgery vulnerability in n/a, published on 27 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24060 exists.

Affected product: n/a. 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-2023-24060/ (Markdown: https://insights.sbomify.com/CVE-2023-24060/index.md)
```

## Sources

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

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