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

> An unauthenticated attacker can exploit a cross-site scripting vulnerability in Oracle Reports Developer to read and modify accessible data via HTTP.

- **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:** 16 Jan 2019
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-jc6x-4pr3-24jx

## What is CVE-2019-2413?

CVE-2019-2413 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Jan 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

Vulnerability in the Oracle Reports Developer component of Oracle Fusion Middleware (subcomponent: Valid Session). The supported version that is affected is 12.2.1.3. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Reports Developer. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Reports Developer, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Reports Developer accessible data as well as unauthorized read access to a subset of Oracle Reports Developer accessible data. CVSS 3.0 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

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

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

It affects 1 product.


Products: Oracle Reports Developer.

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

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

## Is CVE-2019-2413 being exploited?

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

Public exploit code:

- Oracle Reports Developer Component 12.2.1.3 - Cross-site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2026-62608](https://insights.sbomify.com/CVE-2026-62608/): Auth bypass in Oracle Reports Developer (critical 9.9)
- [CVE-2026-62609](https://insights.sbomify.com/CVE-2026-62609/): Auth bypass in Oracle Reports Developer (critical 9.8)
- [CVE-2026-62611](https://insights.sbomify.com/CVE-2026-62611/): Auth bypass in Oracle Reports Developer (critical 9.8)
- [CVE-2026-62614](https://insights.sbomify.com/CVE-2026-62614/): Auth bypass in Oracle Reports Developer (critical 9.8)
- [CVE-2026-62617](https://insights.sbomify.com/CVE-2026-62617/): Auth bypass in Oracle Reports Developer (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-2413 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Jan 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-2413 exists.

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-2413/ (Markdown: https://insights.sbomify.com/CVE-2019-2413/index.md)
```

## Sources

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

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