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

> Attackers can exploit SSRF in the Bon Instagram Carousel plugin to use the server as a proxy for attacks or data exfiltration.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Nov 2023
- **Updated:** 5 Sep 2024
- **Also known as:** GHSA-f48g-5q5h-xx63

## What is CVE-2023-43982?

CVE-2023-43982 is a critical server-side request forgery vulnerability in n/a, published on 3 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Bon Presta boninstagramcarousel between v5.2.1 to v7.0.0 was discovered to contain a Server-Side Request Forgery (SSRF) via the url parameter at insta_parser.php. This vulnerability allows attackers to use the vulnerable website as proxy to attack other websites or exfiltrate data via a HTTP call.

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

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

It affects 1 product.


Products: Bontheme Socialfeed - Photos \& Video Using Instagram Api.

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

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

## Is CVE-2023-43982 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-43982 is a critical server-side request forgery vulnerability in n/a, published on 3 Nov 2023. 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-2023-43982 in the wild and no public exploit code.

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-43982/ (Markdown: https://insights.sbomify.com/CVE-2023-43982/index.md)
```

## Sources

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

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