LiveActive security incident?Get immediate response
CVE Record

CVE-2020-22755: File upload vulnerability in MCMS 5.0 allows attackers to execute arbitrary code via a crafted thumbnail.

File upload vulnerability in MCMS 5.0 allows attackers to execute arbitrary code via a crafted thumbnail. A different vulnerability than CVE-2022-31943.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

MCMS 5.0 has a high-severity thumbnail upload flaw that could let a logged-in attacker run arbitrary code. That can affect confidentiality, integrity, and availability. The provided sources do not show CISA KEV listing, active exploitation, or a named fixed version.

Executive priority

Treat as urgent for any exposed MCMS 5.0 system because successful exploitation could become server code execution. Priority drops if MCMS 5.0 is absent or not reachable by upload-capable users.

Technical view

CVE-2020-22755 is a CWE-434 unrestricted file upload issue in MCMS 5.0 thumbnail handling. CVSS 3.1 is 8.8: network reachable, low complexity, low privileges, no user interaction, unchanged scope, and high CIA impact. Sources distinguish it from CVE-2022-31943.

Likely exposure

Exposure is most likely where MCMS 5.0 is deployed and reachable by users with upload-capable accounts. The structured affected metadata is incomplete, with no vendor, product CPE, or version range beyond the description.

Exploitation context

The CVE record indicates arbitrary code execution through a crafted thumbnail, but the bundle does not provide active exploitation evidence. KEV is false, so do not claim known exploitation based on these sources.

Researcher notes

The evidence is concise and incomplete: it names MCMS 5.0 and thumbnail upload code execution, but affected CPEs and remediation details are missing. Analysis should preserve that uncertainty and avoid extending impact to other MCMS versions.

Mitigation direction

  • Identify any MCMS 5.0 deployments and their internet exposure.
  • Check the MCMS repository and issue 42 for vendor fix guidance.
  • Restrict upload-capable accounts to trusted, necessary users.
  • Reduce external access until remediation status is confirmed.
  • Do not assume a fixed version from these sources alone.

Validation and detection

  • Inventory applications using MCMS and confirm exact version.
  • Review whether thumbnail upload functionality is enabled.
  • Check accounts with upload privileges for necessity and compromise indicators.
  • Review upload and web server logs for unusual thumbnail activity.
  • Track vendor repository or issue updates for remediation details.
Prepared
Confidence
medium
Sources
4

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
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. 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-22755 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2020-22755Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
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.