# CVE-2023-28698: WADE DIGITAL DESIGN CO, LTD. FANTSY - Broken Acesss Control

> Unauthenticated attackers can modify URL parameters to gain administrator privileges and execute arbitrary operations or disrupt service.

- **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:** 2 Jun 2023
- **Updated:** 8 Jan 2025
- **Also known as:** GHSA-w65v-2jvx-6697

## What is CVE-2023-28698?

CVE-2023-28698 is a critical missing authorization vulnerability in WADE DIGITAL DESIGN CO, LTD. FANTSY, published on 2 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Wade Graphic Design FANTSY has a vulnerability of insufficient authorization check. An unauthenticated remote user can exploit this vulnerability by modifying URL parameters to gain administrator privileges to perform arbitrary system operation or disrupt service.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Wddgroup Fantsy.

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

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

## Is CVE-2023-28698 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-28698 is a critical missing authorization vulnerability in WADE DIGITAL DESIGN CO, LTD. FANTSY, published on 2 Jun 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-28698 in the wild and no public exploit code.

Affected product: WADE DIGITAL DESIGN CO, LTD. FANTSY. 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-28698/ (Markdown: https://insights.sbomify.com/CVE-2023-28698/index.md)
```

## Sources

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

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