Munshi XSS via Purchase Inquiry Thread Rendering
Munshi versions up to and including 2026-07-13 are affected through messages or item descriptions in the Purchase Inquiry thread feature. The checked facts list no fix.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Munshi version up to and including 2026-07-13 Message or item description submitted in the Purchase Inquiry thread feature
- 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
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- 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
- 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
Munshi, a business software product from Petpooja, contains a stored cross-site scripting flaw in its Purchase Inquiry thread feature. An logged-in user can save malicious script in item descriptions or messages, which then runs in the browser of anyone who opens that thread, letting the attacker take actions as that user or alter the page each time it is viewed.
Read the original description
Munshi (by Petpooja) before 2026-07-13 contained a stored cross-site scripting vulnerability that allows authenticated users to inject malicious markup through item descriptions or messages submitted in the Purchase Inquiry thread (/purchase-inquiry/thread/{thread-id}), which is assigned to innerHTML during rendering before text cleaning completes. Attackers can store a payload that executes in the browser of another user who opens the affected thread, achieving JavaScript execution and full-page defacement that re-triggers whenever the thread is reopened.
What to do
Check whether your setup matches what the bug needs.
Munshi version up to and including 2026-07-13 Message or item description submitted in the Purchase Inquiry thread featureWorkaround: The checked facts give no workaround. Limiting use of the Purchase Inquiry thread feature is the only step the facts point to, but the facts do not confirm it as a fix.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Petpooja Munshi
through 2026-07-13
Evidence 3
- Exploit
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119735
What does this mean?
Script stored through a Purchase Inquiry thread runs in another user's browser, allowing JavaScript execution and full-page defacement. The defacement repeats whenever the thread is reopened.Source: vulncheck.com
Am I affected, and how do I check?
The advisory lists Munshi versions up to and including 2026-07-13. The affected feature is the Purchase Inquiry thread at /purchase-inquiry/thread/{thread-id}, where messages or item descriptions are submitted.Source: vulncheck.com
What should I do about it?
The checked facts name no fixed version, so no upgrade target can be given. Check the vendor's Petpooja Munshi release notes for a version released after 2026-07-13.Source: vulncheck.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
What if there's no patch?
The checked facts give no workaround. Limiting use of the Purchase Inquiry thread feature is the only step the facts point to, but the facts do not confirm it as a fix.Source: vulncheck.com