LiveActive security incident?Get immediate response
CVE Record

CVE-2020-37072: Victor CMS 1.0 - 'comment_author' Persistent Cross-Site Scripting

Victor CMS 1.0 contains a stored cross-site scripting vulnerability in the 'comment_author' POST parameter that allows attackers to inject malicious scripts. Attackers can submit crafted JavaScript payloads through the comment submission form to execute arbitrary code in victim browsers.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Victor CMS 1.0 has a stored cross-site scripting flaw in the comment author field. An unauthenticated attacker can submit a malicious comment value that later runs script in another user’s browser when viewed. This can support session theft, content tampering, or user impersonation within the affected site context.

Executive priority

Prioritize remediation for internet-facing Victor CMS 1.0 sites, especially where administrators review public comments while authenticated. This is high severity but appears product-specific, with no KEV-backed active exploitation evidence in the provided sources.

Technical view

CVE-2020-37072 is CWE-79 in VictorAlagwu CMSsite/Victor CMS 1.0. The vulnerable parameter is the comment_author POST field. The CVSS 3.1 score is 7.2, vector AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N. Public references include Exploit-DB and VulnCheck advisories.

Likely exposure

Exposure is limited to organizations running Victor CMS/CMSsite version 1.0 with the comment submission functionality reachable by untrusted users. Internet-facing deployments are the primary concern. The source bundle does not identify other affected versions or products.

Exploitation context

A public Exploit-DB entry exists, so proof-of-concept information is public. The source bundle does not show CISA KEV listing or confirmed active exploitation. Stored XSS impact depends on who views submitted comments and what privileges or session data their browser has.

Researcher notes

Evidence is sufficient for affected product, version, parameter, CWE, and public exploit availability. Evidence is incomplete on vendor patch status, fixed versions, and real-world exploitation. Avoid assuming broader CMSsite versions are affected without testing or vendor confirmation.

Mitigation direction

  • Identify any Victor CMS/CMSsite 1.0 deployments.
  • Check the project repository and VulnCheck advisory for vendor guidance.
  • If no fix is available, consider disabling public comments temporarily.
  • Review application code for safe input handling and output encoding.

Validation and detection

  • Inventory web properties for Victor CMS/CMSsite usage and version.
  • Confirm whether the comment_author value is stored and rendered unencoded.
  • Review stored comments for suspicious script-like content.
  • Check access logs for unusual comment submissions.
Prepared
Confidence
high
Sources
5

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-37072 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
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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
4Source 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
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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
VictorAlagwuCMSsite1.0Listed
Weakness

CWE details

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