LiveActive security incident?Get immediate response
CVE Record

CVE-2020-18280: Cross Site Scripting vulnerability found in Phodal CMD v.1.0 allows a local attacker to execute arbitrary c...

Cross Site Scripting vulnerability found in Phodal CMD v.1.0 allows a local attacker to execute arbitrary code via the EMBED SRC function.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a cross-site scripting issue reported in Phodal CMD v1.0. If vulnerable functionality is reachable, attacker-controlled embedded content could run in a user's browser after interaction. The public data is sparse, so urgency depends on whether this software is present and exposed.

Executive priority

Treat as a targeted moderate-risk item. It does not justify emergency response without confirmed exposure, but any confirmed deployment that renders untrusted content should be remediated promptly because browser-side script execution can support account or data compromise.

Technical view

The CVE describes CWE-79 XSS involving the EMBED SRC function, with CVSS 3.1 score 6.1 and vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N. The record names Phodal CMD v1.0, but structured affected vendor/product/CPE data is absent.

Likely exposure

Exposure evidence is limited to the CVE description naming Phodal CMD v1.0. No CPEs or structured affected product metadata are provided, so teams should confirm any use of Phodal CMD or related phodal/md components before prioritizing remediation.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates user interaction is required and the expected impact is limited confidentiality and integrity compromise, not availability loss.

Researcher notes

The record has sparse affected-product data and one GitHub issue reference. Note the wording mismatch between “local attacker” in the description and the network CVSS vector. Avoid broad product assumptions without confirming repository lineage and deployment context.

Mitigation direction

  • Check the upstream GitHub issue and vendor guidance for fixed versions or workarounds.
  • Inventory and remove or upgrade any confirmed Phodal CMD v1.0 deployment.
  • Restrict untrusted embedded content until vendor remediation is confirmed.
  • Apply server-side and client-side sanitization for user-controlled rendered content.
  • Limit access to any affected local or internal tooling.

Validation and detection

  • Confirm whether Phodal CMD v1.0 or related phodal/md code is used.
  • Review rendering paths that accept EMBED SRC or similar embedded content.
  • Verify untrusted content is sanitized before browser rendering.
  • Check whether affected functionality is reachable by non-administrative users.
  • Document findings because public affected-product metadata is incomplete.
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-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-18280 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
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

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

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
2Source 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
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2020-18280Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

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-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.