# CVE-2019-2419: Cross-site scripting in PeopleSoft Enterprise CC Common Application Objects > Low-privileged attackers can exploit a cross-site scripting vulnerability in PeopleSoft Form and Approval Builder to read and modify accessible data. - **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:** 16 Jan 2019 - **Updated:** 2 Oct 2024 - **Also known as:** GHSA-3vq8-3w4f-vmjq ## What is CVE-2019-2419? CVE-2019-2419 is a medium-severity cross-site scripting vulnerability in Oracle Corporation PeopleSoft Enterprise CC Common Application Objects, published on 16 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 Vulnerability in the PeopleSoft Enterprise CC Common Application Objects component of Oracle PeopleSoft Products (subcomponent: Form and Approval Builder). The supported version that is affected is 9.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise CC Common Application Objects. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in PeopleSoft Enterprise CC Common Application Objects, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of PeopleSoft Enterprise CC Common Application Objects accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise CC Common Application Objects accessible data. Note: This Enterprise Common Component is used by all PeopleSoft Application products. Please refer to the MOS Note Doc ID 2493366.1 for patch information. CVSS 3.0 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N). ## Which versions are affected by CVE-2019-2419? It affects 1 product. Products: Oracle Peoplesoft Enterprise Cost Center Common Application Objects. ## How do I fix CVE-2019-2419? No fix has been published for CVE-2019-2419 yet. Limit exposure of the affected software until one is available. ## Is CVE-2019-2419 being exploited? There is no known exploitation of CVE-2019-2419 in the wild and no public exploit code. ## Other vulnerabilities in Oracle Corporation PeopleSoft Enterprise CC Common Application Objects - [CVE-2021-35543](https://insights.sbomify.com/CVE-2021-35543/): Missing authorization in PeopleSoft Enterprise CC Common Application Objects (high 8.1) - [CVE-2023-22090](https://insights.sbomify.com/CVE-2023-22090/): Information disclosure in PeopleSoft Enterprise CC Common Application Objects (medium 6.5) - [CVE-2024-21264](https://insights.sbomify.com/CVE-2024-21264/): Missing authorization in PeopleSoft Enterprise CC Common Application Objects (medium 5.4) - [CVE-2020-2695](https://insights.sbomify.com/CVE-2020-2695/): Information disclosure in PeopleSoft Enterprise CC Common Application Objects (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-2419 and fix it if it is affected. What it is: CVE-2019-2419 is a medium-severity cross-site scripting vulnerability in Oracle Corporation PeopleSoft Enterprise CC Common Application Objects, published on 16 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-2419 in the wild and no public exploit code. Affected product: Oracle Corporation PeopleSoft Enterprise CC Common Application Objects. 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-2419/ (Markdown: https://insights.sbomify.com/CVE-2019-2419/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-2419 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-2419 - OSV: https://osv.dev/vulnerability/CVE-2019-2419 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-2419/ Summaries are generated and may contain mistakes; the official description above is the record.