CVE-2026-61078
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVulnerability in the PeopleSoft Enterprise CC Common Application Objects product of Oracle PeopleSoft (component: Common Application Objects). 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 (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all PeopleSoft Enterprise CC Common Application Objects accessible data as well as unauthorized access to critical data or complete access to all PeopleSoft Enterprise CC Common Application Objects accessible data. CVSS 3.1 Base Score 8.7 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a vulnerability in PeopleSoft Enterprise CC (Customer Center) Common Application Objects version 9.2. It allows low-privileged attackers with network access via HTTP to create, delete, or modify critical data, as well as access critical or complete data within the application. The vulnerability requires human interaction and can impact additional products beyond the directly affected component due to scope change.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 9.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify PeopleSoft CC Common Application Objects installationLocate the PeopleSoft Enterprise installation directory and verify the Common Application Objects component is present. Check installed software listings or PeopleSoft component registry for 'CC Common Application Objects'Affected if The component is installed and running version 9.2
-
Confirm installed version is 9.2Access PeopleSoft Enterprise Administration or component version information. Typically found in PeopleSoft Enterprise Manager, Component Registry, or about the PeopleSoft system page. Compare your installed version to the affected range (9.2)Affected if Installed version matches 9.2 exactly or falls within the 9.2 release line
-
Verify HTTP access is enabledCheck PeopleSoft web configuration files (such as web.xml or psconfig.sh) and web server settings to confirm HTTP listeners are active for the PeopleSoft applicationAffected if HTTP access is enabled and the PeopleSoft web components are reachable via HTTP protocol
-
Assess anti-CSRF protectionsInspect PeopleSoft application configuration for CSRF token enforcement or anti-CSRF measures. Check web.xml for CSRF filter configurations or examine session management settingsAffected if No CSRF tokens or anti-CSRF protections are configured/enabled in the PeopleSoft application
-
Review network accessibilityDetermine if the PeopleSoft admin and application interfaces are exposed to untrusted networks. Check firewall rules, load balancer configurations, and network segmentation for PeopleSoft portsAffected if PeopleSoft interfaces are accessible from untrusted or external networks without proper access restrictions
A defender is affected if they have PeopleSoft Enterprise CC Common Application Objects version 9.2 running with HTTP access enabled, no anti-CSRF protections, and the interface is network-accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply Oracle's published security patches for PeopleSoft Enterprise CC Common Application Objects 9.2. Additionally, restrict network access to PeopleSoft interfaces and implement least-privilege user controls to reduce the attack surface.
- Consultation8.0 h
- Implementation8.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-61078 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-61078 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data