LiveActive security incident?Get immediate response
CVE Record

CVE-2019-16926: Flower 0.9.3 has XSS via a crafted worker name.

Flower 0.9.3 has XSS via a crafted worker name. NOTE: The project author stated that he doesn't think this is a valid vulnerability. Worker name and task name aren’t user facing configuration options. They are internal backend config options and person having rights to change them already has full access

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2019-16926 describes a reported cross-site scripting issue in Flower 0.9.3 through a crafted worker name. The project author disputed its practical validity, saying worker and task names are internal backend configuration, not user-facing settings. No CVSS score, CWE, patch, or active exploitation evidence is provided in the source bundle.

Executive priority

Handle as a low-priority hygiene issue unless Flower is exposed to untrusted users or configuration control is delegated broadly. The main business action is inventory and access control verification, not emergency response.

Technical view

The report claims Flower renders attacker-controlled worker-name content unsafely, enabling XSS if that name is crafted. Available metadata lists affected product and version fields as n/a despite the title naming Flower 0.9.3. The CVE note materially limits impact by asserting only already-privileged backend operators can change the relevant values.

Likely exposure

Exposure is likely limited to organizations running Flower 0.9.3 where untrusted or semi-trusted users can influence worker names or backend configuration. Publicly exposed Flower dashboards would increase concern, but the bundle does not establish internet-exposed exploitation or broad affected-version ranges.

Exploitation context

The only exploitation evidence in the bundle is a public researcher report. The CVE is not in KEV, and no cited source confirms active exploitation. The author’s dispute suggests exploitation may require backend configuration access already equivalent to high privilege.

Researcher notes

Key uncertainty remains: the CVE title says Flower 0.9.3, the reference URL mentions Flower 1.0.0, and structured affected fields are n/a. Treat version scope and exploitability as unconfirmed until validated against project history or vendor guidance.

Mitigation direction

  • Inventory Flower deployments and confirm whether version 0.9.3 is present.
  • Check Flower project guidance because no patch is named in the source bundle.
  • Restrict Flower dashboard access to trusted administrators only.
  • Limit rights to modify worker names and backend task configuration.
  • Monitor vendor or project advisories for clarified affected versions.

Validation and detection

  • Confirm whether Flower is deployed and identify its exact version.
  • Review who can modify worker names or backend worker configuration.
  • Check whether Flower dashboards are reachable from untrusted networks.
  • Look for unusual worker names in operational logs or Flower views.
  • Document uncertainty where affected versions cannot be confirmed from sources.
Prepared
Confidence
medium
Sources
3

Public sources used

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-2019-16926 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
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

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.