# CVE-2026-119735: Munshi XSS via Purchase Inquiry Thread Rendering


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-q6gm-432c-pmpq

## What is CVE-2026-119735?

CVE-2026-119735 is a medium-severity vulnerability in Petpooja Munshi, published on 2 Nov 2026. 

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-119735?


## How do I fix CVE-2026-119735?

No fix has been published for CVE-2026-119735 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119735 being exploited?

There is no known exploitation of CVE-2026-119735 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119735 and fix it if it is affected.

What it is: CVE-2026-119735 is a medium-severity vulnerability in Petpooja Munshi, published on 2 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-119735 in the wild and no public exploit code.

Affected product: Petpooja Munshi. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119735/ (Markdown: https://insights.sbomify.com/CVE-2026-119735/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119735
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119735
- OSV: https://osv.dev/vulnerability/CVE-2026-119735

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119735/
Summaries are generated and may contain mistakes; the official description above is the record.