# CVE-2019-6278: Cross-site scripting in n/a

> Attackers can inject malicious scripts via Markdown input in JPress, potentially leading to session hijacking or code execution.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jan 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-33w3-jv2q-xrfj

## What is CVE-2019-6278?

CVE-2019-6278 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Jan 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

XSS exists in JPress v1.0.4 via Markdown input, or Markdown input with the code input option.

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

## Which versions are affected by CVE-2019-6278?

It affects 1 product.


Products: Jpress Jpress.

## How do I fix CVE-2019-6278?

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

## Is CVE-2019-6278 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-50919](https://insights.sbomify.com/CVE-2024-50919/): File upload in n/a (critical 9.8)
- [CVE-2021-45807](https://insights.sbomify.com/CVE-2021-45807/): Command injection in n/a (critical 9.8)
- [CVE-2024-43033](https://insights.sbomify.com/CVE-2024-43033/): File upload in n/a (high 8.8)
- [CVE-2022-23330](https://insights.sbomify.com/CVE-2022-23330/): Code injection in n/a (high 8.8)
- [CVE-2021-46114](https://insights.sbomify.com/CVE-2021-46114/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6278 and fix it if it is affected.

What it is: CVE-2019-6278 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Jan 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-6278 in the wild and no public exploit code.

Affected product: n/a. 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-2019-6278/ (Markdown: https://insights.sbomify.com/CVE-2019-6278/index.md)
```

## Sources

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

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