LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36525: Linking New Windows Macro cross site scripting

A vulnerability classified as problematic has been found in Linking. This affects an unknown part of the component New Windows Macro. The manipulation leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

LowCVSS 3.5Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2020-36525 is a low-severity cross-site scripting issue in Linking's New Windows Macro component. It could let a remote, low-privileged user influence content that another user must interact with, causing limited integrity impact. Sources do not identify a specific vendor fix, affected versions, or active exploitation.

Executive priority

Treat as low priority unless Linking New Windows Macro is internet-facing, broadly editable, or used in sensitive workflows. The business risk is mainly limited content tampering or browser-side script execution after user interaction, with no sourced evidence of active exploitation.

Technical view

The CVE maps to CWE-79 and CVSS 3.1 score 3.5: network reachable, low complexity, low privileges required, user interaction required, unchanged scope, no confidentiality or availability impact, and low integrity impact. The affected product data is sparse: product Linking, component New Windows Macro, versions listed as n/a.

Likely exposure

Exposure is limited to environments that actually use the Linking product and its New Windows Macro component. The source bundle does not provide CPEs, exact versions, deployment model, or vendor identity, so asset confirmation is the main first step.

Exploitation context

The record says the exploit was publicly disclosed and may be used, but KEV is false and the provided sources do not confirm active exploitation. Successful abuse appears to require low privileges and user interaction, which reduces urgency compared with unauthenticated or automatic compromise paths.

Researcher notes

Key gaps are significant: unspecified vendor, no CPEs, no affected version range, and no named patch. Use CVSS constraints to scope testing carefully. Do not assume broader Linking products are affected without confirming the New Windows Macro component is present.

Mitigation direction

  • Identify whether Linking New Windows Macro is deployed or exposed.
  • Check the maintainer or vendor for version-specific remediation guidance.
  • Apply any vendor update or configuration guidance once confirmed.
  • Reduce access to macro creation or editing to trusted users.
  • Monitor public references for newly published fixes or exploitation evidence.

Validation and detection

  • Search asset inventory for Linking or New Windows Macro usage.
  • Confirm which users can create, edit, or publish New Windows Macro content.
  • Review change history for unexpected macro edits or suspicious content.
  • Check whether compensating controls already restrict macro functionality.
  • Document uncertainty where product version or vendor ownership cannot be confirmed.
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-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
cve · low confidence lookup

CVE-2020-36525 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
Low
CVSS
3.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/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
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
3.5CVSS 3.1LowCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N2.11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.5Low
CVSS 3.1 vector shape for CVE-2020-36525Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/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
unspecifiedLinkingn/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.