# CVE-2026-120190: PostyBirb Plus Submission Description Editor DescriptionInput.tsx cross site scripting


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-ggpr-cj64-vcq3

## What is CVE-2026-120190?

CVE-2026-120190 is a medium-severity vulnerability in PostyBirb Plus, published on 1 Nov 2026. 

### Official description

A security flaw has been discovered in PostyBirb Plus up to 3.1.75. Affected by this vulnerability is an unknown functionality of the file ui/src/views/submissions/submission-forms/form-components/DescriptionInput.tsx of the component Submission Description Editor. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit has been released to the public and may be used for attacks. Upgrading to version 3.1.76 addresses this issue. The patch is identified as 6b11c2345ad98ae59fd5404a9f1024eb1d10c8a4. It is advisable to upgrade the affected component.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-120190 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120190 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120190 is a medium-severity vulnerability in PostyBirb Plus, published on 1 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120190 exists.

Affected product: PostyBirb Plus. 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-120190/ (Markdown: https://insights.sbomify.com/CVE-2026-120190/index.md)
```

## Sources

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

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