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

> Stored XSS in JspMyAdmin2 allows attackers to inject malicious scripts via unsanitized database fields, potentially leading to code execution or data theft.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Feb 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hx95-8gjm-mqg3

## What is CVE-2019-1000004?

CVE-2019-1000004 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

yugandhargangu JspMyAdmin2 version 1.0.6 and earlier contains a Cross Site Scripting (XSS) vulnerability in sidebar and table data that can result in Database fields aren't properly sanitized and allow code injection (Cross-Site Scripting). This attack appears to be exploitable via the payload needs to be stored in the database and the victim must see the db value in question.

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

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

It affects 1 product.


Products: Jspmyadmin Jspmyadmin2.

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

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

## Is CVE-2019-1000004 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-1000004 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-1000004 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-1000004/ (Markdown: https://insights.sbomify.com/CVE-2019-1000004/index.md)
```

## Sources

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

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