LiveActive security incident?Get immediate response
CVE Record

CVE-2020-21733: Sagemcom F@ST3686 v1.0 HUN 3.97.0 has XSS via RgDiagnostics.asp, RgDdns.asp, RgFirewallEL.asp, RgVpnL2tpPpt...

Sagemcom F@ST3686 v1.0 HUN 3.97.0 has XSS via RgDiagnostics.asp, RgDdns.asp, RgFirewallEL.asp, RgVpnL2tpPptp.asp.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-21733 describes cross-site scripting in several web administration pages of Sagemcom F@ST3686 v1.0 HUN 3.97.0. If an administrator or user reaches malicious content while managing the device, browser-side actions could be abused. Public metadata does not provide severity, CVSS, or a confirmed vendor fix.

Executive priority

Treat this as a targeted network-device hygiene issue, not a confirmed emergency. Prioritize asset identification and management-plane restriction, then seek vendor or ISP remediation because public severity and fix data are incomplete.

Technical view

The CVE names XSS in RgDiagnostics.asp, RgDdns.asp, RgFirewallEL.asp, and RgVpnL2tpPptp.asp on Sagemcom F@ST3686 v1.0 HUN 3.97.0. The CVE record lacks CWE, CPE, CVSS, exploit maturity, and remediation details. KEV status is false in the supplied bundle.

Likely exposure

Exposure appears limited to environments using Sagemcom F@ST3686 devices running v1.0 HUN 3.97.0, especially where the web management interface is reachable by administrators, users, or untrusted networks. The source data does not confirm broader affected firmware or products.

Exploitation context

The supplied sources do not show active exploitation, and the CVE is not listed as KEV. Public GitHub references indicate disclosure material exists, but the bundle does not establish real-world attacks or exploit maturity.

Researcher notes

The CVE record is sparse: no CVSS, CWE, CPE, or patch data is provided. The affected product is named in the description, while structured affected fields are n/a. Avoid extrapolating to other Sagemcom models or firmware versions without vendor evidence.

Mitigation direction

  • Check Sagemcom or ISP guidance for firmware updates or replacement advice.
  • Restrict router management access to trusted administrative networks only.
  • Disable remote administration if it is enabled and not required.
  • Segment affected devices from sensitive administrative workstations where practical.
  • Prioritize replacement if no supported firmware or vendor guidance is available.

Validation and detection

  • Inventory Sagemcom F@ST3686 devices and confirm firmware version HUN 3.97.0.
  • Confirm whether web management pages are reachable from untrusted networks.
  • Review vendor or ISP support channels for fixed firmware or advisories.
  • Use non-invasive authenticated assessment in a lab before production testing.
  • Document compensating controls when firmware remediation is unavailable.
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.

cve · low confidence lookup

CVE-2020-21733 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
3Timeline events
1ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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