LiveActive security incident?Get immediate response
CVE Record

CVE-2020-22151: Permissions vulnerability in Fuel-CMS v.1.4.6 allows a remote attacker to execute arbitrary code via a craf...

Permissions vulnerability in Fuel-CMS v.1.4.6 allows a remote attacker to execute arbitrary code via a crafted zip file to the assests parameter of the upload function.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

FUEL CMS 1.4.6 is reported to allow remote arbitrary code execution through a crafted ZIP upload in the assets upload function. The sources do not provide a CVSS score, confirmed patch, or active exploitation evidence, but code execution risk can create serious business impact if exposed.

Executive priority

Treat this as a priority for any internet-facing FUEL CMS deployment because the reported impact is remote code execution. If no FUEL CMS 1.4.6 instance exists, downgrade after documented verification.

Technical view

The CVE maps to CWE-434 and describes unsafe handling of uploaded ZIP content in the upload function’s assets parameter. The reported outcome is arbitrary code execution by a remote attacker. Affected-product metadata is incomplete, so validation should rely on application inventory and the linked project issue.

Likely exposure

Most likely exposed systems are FUEL CMS 1.4.6 deployments where asset uploads are reachable by remote users or exposed administrative workflows. The source bundle lacks CPEs and normalized vendor/product data, so exposure cannot be assumed from scanners alone.

Exploitation context

The CVE source says remote arbitrary code execution is possible via a crafted ZIP file. CISA KEV status is false in the provided bundle, and no cited source confirms active exploitation in the wild.

Researcher notes

Evidence is thin: the CVE names FUEL CMS 1.4.6 and CWE-434, but affected metadata is listed as n/a and no CVSS is provided. Avoid claiming exploit maturity, patch availability, or broader version impact without additional vendor evidence.

Mitigation direction

  • Identify any FUEL CMS 1.4.6 deployments and owners.
  • Check the linked vendor issue and project guidance for fixes.
  • Restrict asset upload access to trusted authenticated administrators.
  • Remove public internet access to administrative upload workflows where feasible.
  • Review upload directory permissions and execution controls.
  • Monitor for unexpected uploaded archives or executable files.

Validation and detection

  • Confirm whether FUEL CMS 1.4.6 is present in inventory.
  • Verify whether the assets upload function is reachable remotely.
  • Check whether upload access is limited to trusted roles.
  • Review web and application logs for unusual upload activity.
  • Inspect upload directories for unexpected ZIPs or executable content.
  • Track the CVE and GitHub issue for remediation updates.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-22151 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.