Stored XSS in Gastromenum's Gastromenum Ticket and QR Menu System

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Gastromenum/Gastromenum Ticket and QR Menu System (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Gastromenum/Gastromenum Ticket and QR Menu System.
2. 2Review the reported fix. Update Gastromenum/Gastromenum Ticket and QR Menu System to 2026.08.31 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Sep 4, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 4, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 4, 2026

Sources and claim methodology

• Source referencesiberguvenlik.gov.tr

Related CVEs

• Unbounded HTTP/1 status-line and chunk-extension buffering in Mint causes memory-exhaustion DoSSame generic ecosystem
• Slink before 1.12.3 Missing Authorization on Image Comment EndpointsSame generic ecosystem
• firecrawl-mcp-server 3.20.2 Arbitrary Local File Read via filePathSame generic ecosystem
• Blinko 1.8.7 Cross-User AI Conversation Read and Write via message tRPC RouterSame generic ecosystem
• Douyin_TikTok_Download_API 4.1.2 SSRF via url parameterSame generic ecosystem
• ConvertX 0.17.0 Arbitrary File Read via LaTeX Input DirectivesSame generic ecosystem