# CVE-2026-60614: Missing authorization in PeopleSoft Enterprise CS Campus Community

> Low-privileged attackers can modify or read data and cause denial of service in PeopleSoft Campus Community via HTTP.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-xjgq-3mrv-jmh3

## What is CVE-2026-60614?

CVE-2026-60614 is a high-severity missing authorization vulnerability in Oracle Corporation PeopleSoft Enterprise CS Campus Community, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the PeopleSoft Enterprise CS Campus Community product of Oracle PeopleSoft (component: Person Data).   The supported version that is affected is 9.2.38. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise CS Campus Community.  Successful attacks of this vulnerability can result in  unauthorized creation, deletion or modification access to critical data or all PeopleSoft Enterprise CS Campus Community accessible data as well as  unauthorized read access to a subset of PeopleSoft Enterprise CS Campus Community accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of PeopleSoft Enterprise CS Campus Community. CVSS 3.1 Base Score 7.1 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:H).

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-60614?

It affects 1 product.


Products: Oracle Peoplesoft Enterprise Campus Software Campus Community.

## How do I fix CVE-2026-60614?

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

## Is CVE-2026-60614 being exploited?

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

## Other vulnerabilities in Oracle Corporation PeopleSoft Enterprise CS Campus Community

- [CVE-2026-60594](https://insights.sbomify.com/CVE-2026-60594/): Auth bypass in PeopleSoft Enterprise CS Campus Community (high 8.8)
- [CVE-2026-60603](https://insights.sbomify.com/CVE-2026-60603/): Auth bypass in PeopleSoft Enterprise CS Student Records (high 8.8)
- [CVE-2026-60615](https://insights.sbomify.com/CVE-2026-60615/): Auth bypass in PeopleSoft Enterprise CS Campus Community (high 8.2)
- [CVE-2026-60599](https://insights.sbomify.com/CVE-2026-60599/): Missing authorization in PeopleSoft Enterprise CS Student Records (high 8.1)
- [CVE-2026-46851](https://insights.sbomify.com/CVE-2026-46851/): Code injection in PeopleSoft Enterprise CS Campus Community (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-60614 and fix it if it is affected.

What it is: CVE-2026-60614 is a high-severity missing authorization vulnerability in Oracle Corporation PeopleSoft Enterprise CS Campus Community, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-60614 in the wild and no public exploit code.

Affected product: Oracle Corporation PeopleSoft Enterprise CS Campus Community. 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-2026-60614/ (Markdown: https://insights.sbomify.com/CVE-2026-60614/index.md)
```

## Sources

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

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