# CVE-2026-61103: Information disclosure in PeopleSoft Enterprise CS Campus Community

> An attacker on the local network can access sensitive data and modify some records in PeopleSoft Campus Community.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-8xg5-27v2-5c9m

## What is CVE-2026-61103?

CVE-2026-61103 is a medium-severity vulnerability in Oracle Corporation PeopleSoft Enterprise CS Campus Community, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in the PeopleSoft Enterprise CS Campus Community product of Oracle PeopleSoft (component: Security).   The supported version that is affected is 9.2.38. Difficult to exploit vulnerability allows unauthenticated attacker with access to the physical communication segment attached to the hardware where the PeopleSoft Enterprise CS Campus Community executes to compromise PeopleSoft Enterprise CS Campus Community.  Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all PeopleSoft Enterprise CS Campus Community accessible data as well as  unauthorized update, insert or delete access to some of PeopleSoft Enterprise CS Campus Community accessible data. CVSS 3.1 Base Score 5.9 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N).

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Oracle Peoplesoft Enterprise Campus Software Campus Community.

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

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

## Is CVE-2026-61103 being exploited?

There is no known exploitation of CVE-2026-61103 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-61103 and fix it if it is affected.

What it is: CVE-2026-61103 is a medium-severity vulnerability in Oracle Corporation PeopleSoft Enterprise CS Campus Community, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61103 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-61103/ (Markdown: https://insights.sbomify.com/CVE-2026-61103/index.md)
```

## Sources

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

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