# CVE-2026-108724: Sylius through 2.3.0 Authorization Bypass via Shop API Product-Review Endpoint

> Unauthenticated attackers can bypass moderation filters to read unmoderated and rejected product reviews via the Shop API.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-8cf2-xcwc-ppqc

## What is CVE-2026-108724?

CVE-2026-108724 is a medium-severity missing authorization vulnerability in Sylius, published on 11 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sylius through 2.3.0 contains an authorization bypass vulnerability that allows unauthenticated attackers to read unmoderated and rejected product reviews because the AcceptedExtension filter is not applied to the item operation. Attackers can enumerate sequential ids on GET /api/v2/shop/product-reviews/{id} to retrieve review titles, ratings, comments, timestamps and author first names, bypassing merchant moderation.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-108724?


## How do I fix CVE-2026-108724?

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

## Is CVE-2026-108724 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-108724 and fix it if it is affected.

What it is: CVE-2026-108724 is a medium-severity missing authorization vulnerability in Sylius, published on 11 Oct 2026. 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-2026-108724 in the wild and no public exploit code.

Affected product: Sylius. 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-2026-108724/ (Markdown: https://insights.sbomify.com/CVE-2026-108724/index.md)
```

## Sources

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

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