dbcve.org
FantasyApplication · Wddgroup

CVE-2023-28699

HIGH · 8.8 CVSS v3.1 Published 2023-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Wade Graphic Design FANTSY has a vulnerability of insufficient filtering for file type in its file update function. An authenticated remote attacker with general user privilege can exploit this vulnerability to upload a PHP file containing a webshell to perform arbitrary system operation or disrupt service.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The FANTSY application contains an arbitrary file upload vulnerability in its file update function due to insufficient filtering of file types. An authenticated attacker with standard user privileges can upload PHP files containing webshells, enabling arbitrary command execution on the host system.

MitigationImplement strict allowlist-based file type validation in the upload function, checking both file extension and MIME type, and inspecting file content (magic bytes) to verify the actual file type before allowing uploads.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FantasyApplication
Affected:= 2.1.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Wddgroup Fantasy application is installed
    Locate the Fantasy application installation directory or check for web server configs referencing 'fantasy' or 'Wddgroup'
    Affected if The Fantasy application is present on the system
  2. Determine installed Fantasy version
    Check application version file, about page, or version metadata within the installation directory
    Affected if Version is 2.1.8 exactly (the specific affected version)
  3. Verify file upload functionality exists
    Locate the file upload/update function in the application - check for upload forms, endpoints handling file uploads, or modules related to file management
    Affected if File upload functionality is present and accessible to standard users
  4. Confirm authentication is enabled for upload function
    Check if the upload endpoint requires valid user credentials and is accessible to standard (non-admin) authenticated users
    Affected if Standard authenticated users can access the upload function without elevated privileges

System is affected if Wddgroup Fantasy version 2.1.8 is installed and the file upload function is accessible to authenticated standard users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based file type validation in the upload function, checking both file extension and MIME type, and inspecting file content (magic bytes) to verify the actual file type before allowing uploads.

Recommended fix Moderate confidence

Contact vendor for fixed release (request version beyond 2.1.8)

  1. Contact the vendor (Wade Graphic Design/Fantasy) directly to request the patched version that addresses CVE-2023-28699
  2. Verify the file upload function implements proper file type validation (e.g., whitelist approach, MIME type checking, magic byte verification)
  3. Restrict file upload functionality to only trusted, authenticated users if business requirement allows
  4. Implement web server configuration to prevent execution of uploaded files (e.g., move uploads to non-executable directory, use .htaccess restrictions)
  5. Test the patch or mitigation by attempting to upload a non-PHP file with PHP extension to confirm filtering works

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fantasy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28699 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-28699 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data