FoodCoopShop Server-Side Request Forgery vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2023-46725: 0.56% estimated exploitation activity in the next 30 days; percentile 46.88 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

There is a potential SSRF vulnerability in foodcoopshop. Since there is no security policy on your Github, I tried to use the emails to contact you. The potential issue is in the Network module, where a manufacturer account can use the /api/updateProducts.json endpoint to make the server send a request to arbitrary host. For example, use will make the server send a request to localhost:8888. This means that it can be used as a proxy into the internal network where the server is. To make matters worse, the checks on valid image is not enough. There is time of check time of use issue there. For example, by using a custom server that returns 200 on HEAD requests, then return a valid image on first GET request and then a 302 redirect to final target on second GET request, the server will copy whatever file at the redirect destination, making this a full SSRF. (An example python server that can do this is at https://pastebin.com/8K5Brwbq This will make the server download whatever at the…

Published by the source

2 Nov 2023, 20:53 UTC

Last modified by the source

9 Nov 2023, 21:59 UTC

Source last checked

26 Oct 2026, 14:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jhww-fx2j-3rf7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-46725

Advisory: FoodCoopShop Server-Side Request Forgery vulnerability
IDs: CVE-2023-46725, GHSA-jhww-fx2j-3rf7
Record: https://patchnext.com/advisories/cve-2023-46725 (revision 1, source checked 26 Oct 2026, 14:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: foodcoopshop/foodcoopshop 3.6.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist foodcoopshop/foodcoopshop: affected >= 3.2.0, < 3.6.1; fixed in 3.6.1

## Suggested inspection (read-only)
- Packagist foodcoopshop/foodcoopshop: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on foodcoopshop/foodcoopshop.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jhww-fx2j-3rf7 (GitHub-reviewed advisory GHSA-jhww-fx2j-3rf7 lists affected ranges: Packagist foodcoopshop/foodcoopshop >=3.2.0 <3.6.1)

Commands are suggestions: review each one before running it.