CVE Tools

CVE-2022-46020

Public exploit available. Not confirmed exploited in the wild yet. No fix published yet.

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

Steps

Written by AI from the record
  1. Check whether you are running WBCE CMS version 1.5.4 — log into your admin panel or ask whoever manages your site.
  2. If you are, restrict or disable file upload features in the admin panel until a fix is confirmed.
  3. Contact the WBCE CMS team or your web developer to ask if a security patch for this issue has been released, since no official fix is currently documented.
  4. If no patch exists, consider blocking public access to the admin/upload area (e.g., via IP restriction or a web application firewall) as a temporary safeguard.
  5. Once a patched version is available, upgrade immediately and verify the upload function rejects disguised file types.

What it is

From the CVE record

WBCE CMS v1.5.4 can implement getshell by modifying the upload file type.

In plain language

Written by AI from the record

A serious flaw in WBCE CMS version 1.5.4 lets an attacker upload a disguised malicious file and take over your website completely, with no login needed — treat this as a real risk if you run this software.

Unauthenticated remote code execution in WBCE CMS 1.5.4 via improper file-type validation on upload (CWE-434), allowing attackers to disguise a malicious script as an allowed file type and achieve full server compromise.

If you're affected

  • Full website takeover
  • Customer data exposure
  • Website defacement
  • Malware/ransomware hosting
  • Operational disruption

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS99th
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

1 source with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

39% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

7 events over 1280 days, from the signal feeds we watch.

  1. EPSS band changehigh → moderate
  2. Public exploit / PoCsource: github-pocnuclei check added
  3. Record updated
  4. Publishedweakness classified, att&ck mapped

Affected products

And 1 more affected product. See all after sign-in

Technical detail

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

Scored 9.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Wbce Cms, not every advisory. This one: public exploit.