# CVE-2022-21281: Cross-site request forgery in Primavera Portfolio Management

> High-privileged attackers can exploit CSRF to modify or read data in Oracle Primavera Portfolio Management, requiring user interaction.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Jan 2022
- **Updated:** 24 Sep 2024
- **Also known as:** GHSA-995f-c44p-x3jp

## What is CVE-2022-21281?

CVE-2022-21281 is a medium-severity vulnerability in Oracle Corporation Primavera Portfolio Management, published on 19 Jan 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Primavera Portfolio Management product of Oracle Construction and Engineering (component: Web Access). Supported versions that are affected are 18.0.0.0-18.0.3.0, 19.0.0.0-19.0.1.2, 20.0.0.0 and 20.0.0.1. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Primavera Portfolio Management. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Primavera Portfolio Management, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Primavera Portfolio Management accessible data as well as unauthorized read access to a subset of Primavera Portfolio Management accessible data. CVSS 3.1 Base Score 4.8 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N).

## Which versions are affected by CVE-2022-21281?

It affects 1 product.


Products: Oracle Primavera Portfolio Management.

## How do I fix CVE-2022-21281?

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

## Is CVE-2022-21281 being exploited?

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

## Other vulnerabilities in Oracle Corporation Primavera Portfolio Management

- [CVE-2022-21269](https://insights.sbomify.com/CVE-2022-21269/): Cross-site scripting in Primavera Portfolio Management (medium 6.1)
- [CVE-2020-14528](https://insights.sbomify.com/CVE-2020-14528/): Cross-site scripting in Primavera Portfolio Management (medium 6.1)
- [CVE-2020-2562](https://insights.sbomify.com/CVE-2020-2562/): Cross-site scripting in Primavera Portfolio Management (medium 6.1)
- [CVE-2020-14527](https://insights.sbomify.com/CVE-2020-14527/): Information disclosure in Primavera Portfolio Management (medium 5.9)
- [CVE-2020-14549](https://insights.sbomify.com/CVE-2020-14549/): Information disclosure in Primavera Portfolio Management (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-21281 and fix it if it is affected.

What it is: CVE-2022-21281 is a medium-severity vulnerability in Oracle Corporation Primavera Portfolio Management, published on 19 Jan 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-21281 in the wild and no public exploit code.

Affected product: Oracle Corporation Primavera Portfolio Management. 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-2022-21281/ (Markdown: https://insights.sbomify.com/CVE-2022-21281/index.md)
```

## Sources

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

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