CVE-2026-61207
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 SCM eProcurement product of Oracle PeopleSoft (component: Manage Requisition Status). The supported version that is affected is 9.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise SCM eProcurement. While the vulnerability is in PeopleSoft Enterprise SCM eProcurement, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all PeopleSoft Enterprise SCM eProcurement accessible data as well as unauthorized update, insert or delete access to some of PeopleSoft Enterprise SCM eProcurement accessible data. CVSS 3.1 Base Score 9.3 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/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 · moderate confidenceUnauthenticated remote vulnerability in PeopleSoft Enterprise SCM eProcurement (Manage Requisition Status component) version 9.2 allows attackers via HTTP to access, modify, or delete data in the eProcurement module. The CVSS vector indicates a scope change (S:C) meaning attacks can impact additional products beyond the eProcurement module.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/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 eProcurement installationCheck if the PeopleSoft Enterprise SCM eProcurement application is installed. Look for eProcurement-related web applications, check PeopleSoft component navigation for 'eProcurement' menu items, or query the PSSTATUS or PSPRCOPTIONS tables in the PeopleSoft database for eProcurement module presence.Affected if eProcurement module is present in the PeopleSoft environment
-
Verify PeopleSoft versionAccess PeopleSoft About page (typically via 'About This Page' link or psAbout.htm), check the PeopleSoft banner at login, or query the PSVERSION table for the application release version. Compare the installed version to 9.2.Affected if Installed version is PeopleSoft 9.2
-
Confirm Manage Requisition Status component exposureCheck if the 'Manage Requisition Status' component (typically accessed via eProcurement > Requisitions > Manage Requisition Status) is accessible. This component is often exposed through the /psc/ps/ URL path. Verify via web browser or by checking the PSPCMPROG table for the component definition.Affected if The Manage Requisition Status component is present and accessible via web interface
-
Test HTTP endpoint accessibilityDetermine if eProcurement HTTP endpoints are reachable from external networks. Use a web browser or curl command to attempt access to the eProcurement login page from outside the internal network. Check if port 80/443 is exposed to untrusted networks.Affected if eProcurement HTTP/HTTPS endpoints are accessible from untrusted networks or the internet
-
Verify authentication enforcementAttempt to access the Manage Requisition Status component without credentials. If the vulnerability exists, the application may return data or error messages without proper authentication. Check whether the component enforces authentication or allows unauthenticated access.Affected if The component can be accessed or returns data without valid authentication credentials
The environment is affected if PeopleSoft Enterprise SCM eProcurement version 9.2 is installed AND the Manage Requisition Status component is accessible via HTTP without requiring authentication, especially if exposed to untrusted networks.
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 the Oracle PeopleSoft Enterprise SCM 9.2 security patch for this vulnerability. Restrict network access to PeopleSoft HTTP endpoints to trusted sources as an interim control.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-61207 — 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-61207 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