LiveActive security incident?Get immediate response
CVE Record

CVE-2020-28727: Cross-site scripting (XSS) exists in SeedDMS 6.0.13 via the folderid parameter to views/bootstrap/class.Dro...

Cross-site scripting (XSS) exists in SeedDMS 6.0.13 via the folderid parameter to views/bootstrap/class.DropFolderChooser.php.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-28727 is a reported cross-site scripting issue in SeedDMS 6.0.13. A web parameter named folderid in the DropFolderChooser view may allow browser-side script injection. The sources do not provide CVSS, confirmed exploitation, or a named fixed release, so urgency depends on whether SeedDMS is exposed and actively used.

Executive priority

Treat this as a targeted web-application hygiene issue, not a confirmed emergency. Prioritize exposed SeedDMS 6.0.13 systems, especially where document access involves sensitive business data or external users.

Technical view

The CVE states that SeedDMS 6.0.13 has XSS through the folderid parameter to views/bootstrap/class.DropFolderChooser.php. No CWE, CVSS vector, exploit evidence, authentication requirement, or affected-version range beyond 6.0.13 is provided in the source bundle.

Likely exposure

Organizations running SeedDMS 6.0.13 are the only clearly identified exposure. Risk is higher if the application is reachable by untrusted users or supports document workflows involving many authenticated users.

Exploitation context

The source bundle does not show active exploitation, and this CVE is not listed as KEV. The public description identifies the vulnerable parameter but does not provide exploit maturity, attacker prerequisites, or observed campaigns.

Researcher notes

Evidence is sparse: the CVE description names the parameter and file, but not the vulnerable code path details, fixed version, CVSS, or exploit status. Use the SourceForge references to confirm the patch history before assigning final severity.

Mitigation direction

  • Inventory SeedDMS deployments and identify any running version 6.0.13.
  • Review SeedDMS project guidance and release files for an official fix or upgrade path.
  • Restrict SeedDMS access to trusted networks or users until remediation is confirmed.
  • Apply vendor-supported updates after validating compatibility in staging.

Validation and detection

  • Confirm whether views/bootstrap/class.DropFolderChooser.php exists in deployed SeedDMS instances.
  • Verify application version information for SeedDMS 6.0.13 exposure.
  • Review access logs for unusual requests involving the folderid parameter.
  • Validate in a safe test environment that folderid output is properly encoded.
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-28727 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.