CVE-2026-61804: myTinyWMS has Stored Cross-Site Scripting (XSS) in Product and Category Management
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
myTinyWMS is a free, open-source warehouse management system. Prior to version 1.6.4, `Product (Artikel)` and `Category` management store the `name` parameter without adequate backend sanitization and render raw database strings through unescaped Blade output in dynamic table cells, including `article/index.blade.php` and `category/index.blade.php`. An authenticated attacker can save malicious input through product creation or category forms. When another user, including a worker or administrator, opens the corresponding product sheet, category listing or dashboard, the stored JavaScript executes in that user’s browser context. This can enable cross-user script execution, session theft and administrative takeover. This issue is fixed in version 1.6.4.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-10-30).
Weakness: CWE-79: Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’)
How it can be exploited
Exploitable over the network with low attack complexity needing high privileges and a user must take an action. Impact: confidentiality high, integrity high, availability none. CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: total.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 4 references on Exploit Observer
Live scores
- EPSS
- 0.003
low predicted chance of attack - VEDAS
- 0.986
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| myTinyWMS | version < 1.6.4 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-61804 myTinyWMS - Stored XSS via Product/Category name parameter. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-61804 myTinyWMS - Stored XSS via Product/Category name parameter"; flow:established,to_server; http.method; content:"POST"; http.request_body; content:"name="; nocase; fast_pattern; pcre:"/name=[^&]*(?:<|%3c)\s*(?:\/?\s*)?(?:script|svg|img|iframe|body|details|object|embed|on[a-z]+\s*(?:=|%3d))/i"; classtype:web-application-attack; reference:cve,CVE-2026-61804; reference:url,https://www.exploit.observer/?keyword=CVE-2026-61804&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=mytinywms&match=exact; sid:1105200; rev:1;)
CVE-2026-61804.rules on GitHub
References
Other references
- https://github.com/myTinyWMS/myTinyWMS/security/advisories/GHSA-gw9m-vphv-gxm5 (x_refsource_CONFIRM)
- https://github.com/myTinyWMS/myTinyWMS/commit/a01af6bb0e8f4013125c47c795a4736e7cbac7ec (x_refsource_MISC)
- https://github.com/myTinyWMS/myTinyWMS/tree/v1.6.4 (x_refsource_MISC)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
