CVE-2026-61235
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 HCM Global Payroll Switzerland product of Oracle PeopleSoft (component: Global Payroll for Switzerland). The supported version that is affected is 9.2. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise HCM Global Payroll Switzerland. While the vulnerability is in PeopleSoft Enterprise HCM Global Payroll Switzerland, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of PeopleSoft Enterprise HCM Global Payroll Switzerland. CVSS 3.1 Base Score 9.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).
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 · moderate confidenceA critical vulnerability in Oracle PeopleSoft Enterprise HCM Global Payroll Switzerland (v9.2) allows high-privileged attackers with network access via HTTP to achieve complete takeover of the Global Payroll component. The CVSS 9.1 score indicates full confidentiality, integrity, and availability compromise, with scope change potentially affecting additional PeopleSoft products.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
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.
-
Confirm PeopleSoft HCM versionQuery the PeopleSoft Application Designer or check the PSVERSION table for the HCM application release version. Look for version 9.2 specifically as noted in the affected versions.Affected if The installed version is exactly 9.2 or falls within an unpatched 9.2.x release branch
-
Identify Global Payroll Switzerland moduleCheck the PeopleSoft Component Registry or navigate to the Global Payroll > Switzerland menu path in the PeopleSoft Internet Architecture to confirm the module is installed and accessible.Affected if The Global Payroll Switzerland module is present and accessible in the PeopleSoft menu structure
-
Verify HTTP listener exposureReview the PeopleSoft web server configuration (web.xml or ibconfig) and network firewall rules to determine if the PeopleSoft HTTP ports (typically 80, 443, or custom ports) are exposed to untrusted networks.Affected if HTTP/HTTPS listeners are reachable from untrusted or external network segments without proper access controls
-
Assess high-privileged account accessQuery the PeopleSoft Security tables (PSOPRDEFN, PSROLEDEFN) or review the PeopleSoft Pure Internet Architecture login page to identify accounts with elevated privileges that could be targeted.Affected if High-privileged operator accounts exist in the system and are accessible via the HTTP interface
A system is affected if it runs PeopleSoft HCM version 9.2 with the Global Payroll Switzerland module installed and the HTTP 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 PeopleSoft Enterprise HCM patch for version 9.2 when available; restrict network access to PeopleSoft HTTP services to trusted users only and follow least-privilege principles for high-privileged accounts.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-61235 — 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-61235 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