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

> Attackers can exploit SSRF in Forem to access internal network resources and sensitive information via crafted requests.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Mar 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-v5g3-mw88-c3jm

## What is CVE-2023-27160?

CVE-2023-27160 is a high-severity server-side request forgery vulnerability in n/a, published on 31 Mar 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

forem up to v2022.11.11 was discovered to contain a Server-Side Request Forgery (SSRF) via the component /articles/{id}. This vulnerability allows attackers to access network resources and sensitive information via a crafted POST request.

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

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

It affects 1 product.


Products: Forem Forem.

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

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

## Is CVE-2023-27160 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-27160 is a high-severity server-side request forgery vulnerability in n/a, published on 31 Mar 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27160 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-27160/ (Markdown: https://insights.sbomify.com/CVE-2023-27160/index.md)
```

## Sources

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

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