CVE-2022-21272
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 PeopleTools product of Oracle PeopleSoft (component: Portal). Supported versions that are affected are 8.57, 8.58 and 8.59. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in PeopleSoft Enterprise PeopleTools, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of PeopleSoft Enterprise PeopleTools accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise PeopleTools accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 · high confidenceCVE-2022-21272 is an unauthenticated vulnerability in the Portal component of PeopleSoft Enterprise PeopleTools versions 8.57, 8.58, and 8.59. Attackers with network access via HTTP can exploit this flaw (requiring human interaction) to achieve unauthorized read access to a subset of accessible data and unauthorized insert/update/delete access to some accessible data.
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= 8.57= 8.58= 8.59CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 PeopleTools versionLocate the PeopleTools version installed in your environment. This is typically visible on the PeopleSoft sign-in page, in the About page, or can be queried from the PSVERSION system table in the database.Affected if The installed PeopleTools version is 8.57, 8.58, or 8.59 specifically.
-
Confirm Portal component is enabledVerify whether the PeopleSoft Portal component is configured and active. This can be checked via the PeopleSoft Portal Administration screens or by accessing the portal URL endpoint.Affected if The Portal component is enabled and accessible in the affected PeopleTools versions.
-
Determine HTTP service exposureCheck if the PeopleSoft HTTP services (web entry points) are exposed to the network. Review web server configuration, load balancer settings, or firewall rules that control access to PeopleSoft URLs.Affected if PeopleSoft HTTP services are reachable from network locations beyond trusted internal users.
-
Assess user access to PortalEvaluate whether the Portal is accessible to untrusted or unauthenticated users. Check the authentication configuration and whether guest or anonymous access is permitted.Affected if Untrusted or unauthenticated users can access the Portal component in the affected versions.
Your environment is affected if you are running PeopleTools version 8.57, 8.58, or 8.59 with the Portal component enabled and accessible via HTTP to untrusted users.
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.
dbcve · scopedApply the Oracle Critical Patch Update addressing this vulnerability to affected PeopleSoft Enterprise PeopleTools installations. If immediate patching is not feasible, restrict network access to the PeopleSoft HTTP services and implement additional authentication layers on the Portal component.
PeopleTools 8.60 or later (or apply Jan 2022 CPU patch to affected versions)
- 1. Review Oracle's Critical Patch Update advisory for January 2022 (or subsequent CPU) to obtain the specific patch for CVE-2022-21272.
- 2. Confirm current PeopleTools version by navigating to PeopleTools > About > About PeopleTools.
- 3. Download and apply the appropriate CPU patch from Oracle Support (My Oracle Support).
- 4. After patching, clear the application server cache and web server cache.
- 5. Restart the PeopleSoft application server, web server, and process scheduler.
- 6. Verify the fix by confirming the PeopleTools version and testing Portal functionality.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21272 — 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-2022-21272 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