# CVE-2022-3694: Syncee - Global Dropshipping < 1.0.10 - Authentication Token Disclosure

> An attacker can obtain the administrator token to take over the administrator account in the Syncee 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:** 5 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-88hh-8fwc-jjch

## What is CVE-2022-3694?

CVE-2022-3694 is a high-severity vulnerability in Unknown Syncee, published on 5 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Syncee WordPress plugin before 1.0.10 leaks the administrator token that can be used to take over the administrator's account.

## Which versions are affected by CVE-2022-3694?

It affects 1 product.


Products: Syncee Syncee - Global Dropshipping.

## How do I fix CVE-2022-3694?

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

## Is CVE-2022-3694 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3694 and fix it if it is affected.

What it is: CVE-2022-3694 is a high-severity vulnerability in Unknown Syncee, published on 5 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3694 exists.

Affected product: Unknown Syncee. 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-2022-3694/ (Markdown: https://insights.sbomify.com/CVE-2022-3694/index.md)
```

## Sources

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

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