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

> Authenticated attackers can exploit a blind SSRF vulnerability in Bar Assistant to execute arbitrary code via unvalidated image processing parameters.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 10 Jan 2024
- **Updated:** 3 Jun 2025
- **Also known as:** GHSA-j9ch-j53g-49hj

## What is CVE-2023-49471?

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

### Official description

Blind Server-Side Request Forgery (SSRF) vulnerability in karlomikus Bar Assistant before version 3.2.0 does not validate a parameter before making a request through Image::make(), which could allow authenticated remote attackers to execute arbitrary code.

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

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

It affects 1 product.


Products: Barassistant Bar Assistant.

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

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

## Is CVE-2023-49471 being exploited?

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

Public exploit code:

- https://github.com/zunak/CVE-2023-49471 (github_poc): https://github.com/zunak/CVE-2023-49471

## Fix prompt for AI coding agents

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

What it is: CVE-2023-49471 is a high-severity server-side request forgery vulnerability in n/a, published on 10 Jan 2024. 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-49471 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-49471/ (Markdown: https://insights.sbomify.com/CVE-2023-49471/index.md)
```

## Sources

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

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