Security readout for executives and security teams
Plain-English summary
Locust versions before 1.3.2 had a stored XSS issue in the Web UI. The risk matters mainly when the Locust UI is exposed to outside or untrusted users, which the CVE notes violates expected usage. Public evidence does not show active exploitation.
Executive priority
Prioritize any externally reachable Locust Web UI. Internal-only, properly restricted deployments are lower urgency, but upgrading old versions is still prudent.
Technical view
CVE-2020-28364 is a stored cross-site scripting vulnerability in the Locust Web UI before version 1.3.2. The provided record does not include CVSS, CWE, payload details, or broad affected CPE data. Exposure depends on whether the Locust Web UI is reachable by untrusted users.
Likely exposure
Organizations are most exposed if Locust is running below 1.3.2 and its Web UI is reachable from the internet, partners, or untrusted internal users.
Exploitation context
The source bundle provides no KEV listing and no cited evidence of active exploitation. Stored XSS generally requires malicious content to persist in the UI, but specific exploit mechanics are not provided.
Researcher notes
Evidence is limited to the CVE description and Locust changelog reference. No CVSS vector, CWE, detailed affected CPEs, or confirmed exploitation evidence is included in the bundle.
Mitigation direction
- Upgrade Locust to version 1.3.2 or later.
- Do not expose the Locust Web UI to untrusted networks.
- Restrict access to trusted operators through network controls.
- Review Locust changelog and vendor guidance for related fixes.
Validation and detection
- Inventory Locust deployments and installed versions.
- Confirm all exposed instances run Locust 1.3.2 or later.
- Verify the Web UI is not internet-accessible.
- Check access controls for testing and load-generation environments.
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.
CVE-2020-28364 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://docs.locust.io/en/stable/changelog.htmlCVE reference · x_refsource_MISC
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.