# CVE-2026-54846: WordPress Syncee Premium Dropshipping & Wholesale plugin <= 1.0.27 - Broken Access Control vulnerability

> Unauthenticated attackers can bypass access controls in the Syncee Premium Dropshipping & Wholesale WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-fmxq-8fpc-g567

## What is CVE-2026-54846?

CVE-2026-54846 is a high-severity missing authorization vulnerability in akosglys Syncee Premium Dropshipping &amp; Wholesale, published on 26 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthenticated Broken Access Control in Syncee Premium Dropshipping &amp; Wholesale <= 1.0.27 versions.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-54846 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54846 is a high-severity missing authorization vulnerability in akosglys Syncee Premium Dropshipping &amp; Wholesale, published on 26 Jun 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-54846 in the wild and no public exploit code.

Affected product: akosglys Syncee Premium Dropshipping &amp; Wholesale. 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-54846/ (Markdown: https://insights.sbomify.com/CVE-2026-54846/index.md)
```

## Sources

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

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