Security readout for executives and security teams
Plain-English summary
PDW File Browser has cross-site scripting flaws that can let a logged-in attacker plant or trigger JavaScript in another user’s browser. This could expose session data or alter actions inside the file browser. The issue is medium severity, but risk rises if the tool is internet-facing or used by many semi-trusted users.
Executive priority
Prioritize remediation for internet-facing or shared deployments. This is not a critical infrastructure-level flaw, but it can enable browser-session compromise and unauthorized actions inside affected file-browser workflows.
Technical view
The source bundle describes stored and reflected XSS in PDW File Browser version 1.3 / <=1.3 via file rename and path parameters. CVSS 3.1 is 5.4: network reachable, low complexity, low privileges required, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact.
Likely exposure
Exposure is likely limited to environments running PDW File Browser where attackers can authenticate or influence authenticated users. Public or broadly shared file-browser deployments are more exposed than tightly restricted administrative tools.
Exploitation context
An ExploitDB reference exists, but the bundle does not show CISA KEV listing or evidence of active exploitation. Treat exploit availability as public proof-of-concept visibility, not confirmed in-the-wild exploitation.
Researcher notes
Evidence is sufficient for XSS classification and basic exposure analysis. Patch status is not established in the provided bundle, and the affected-version metadata is limited, so confirm details against vendor and advisory records before closing risk.
Mitigation direction
- Inventory PDW File Browser deployments and confirm whether version 1.3 or earlier is present.
- Check vendor repository and advisory sources for fixed-release or replacement guidance.
- Restrict access to trusted users and trusted networks where feasible.
- Review file names and paths for suspicious script-like content.
- Consider disabling exposed instances until remediation direction is confirmed.
Validation and detection
- Confirm the exact deployed product and version against PDW File Browser records.
- Map who can authenticate and rename files or control path parameters.
- Review application logs and stored filenames for suspicious XSS indicators.
- Validate output encoding behavior in a controlled staging environment.
- Confirm any compensating access controls cover all exposed routes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2020-36988 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
4.8MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-48947CVE reference, VulnCheck · exploit
- PDW File Browser GitHub RepositoryCVE reference, VulnCheck · product
- VulnCheck Advisory: PDW File Browser <= v1.3 - Cross-Site Scripting (XSS)CVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.