myTinyWMS has Stored Cross-Site Scripting (XSS) in Product and Category Management
Affects myTinyWMS v1.6.3, where product and category name inputs are stored and output without escaping. CVSS rates it 8.1 High. Fixed in 1.6.4.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.6.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
myTinyWMS, a free open-source warehouse management system, is affected by a stored cross-site scripting flaw in its product and category management pages. An attacker with a logged-in account can plant malicious script through product or category names, which then runs in the browsers of other users, such as workers or administrators, potentially allowing session theft and control of their accounts.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- myTinyWMS myTinyWMS
fixed in 1.6.4
References 3
GitHub · myTinyWMS/myTinyWMS
Questions about CVE-2026-61804
What does this mean?
Text entered in the product (Artikel) and category name fields is saved without proper back-end sanitizing and is later displayed without output escaping. The advisory says the stored payload then runs automatically in other users' contexts, which can enable session cloning or administrative takeover.Source: github.com
Am I affected, and how do I check?
The advisory lists myTinyWMS v1.6.3 as affected, and the product range is marked as fixed in 1.6.4. The installed version can be checked in the application's version information.Source: github.com
What should I do about it?
Upgrade to myTinyWMS 1.6.4, the fixed version listed for the product.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data