CVE-2022-21520
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: Fluid Core). Supported versions that are affected are 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 (scope change). 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 · moderate confidenceVulnerability in Oracle PeopleSoft Enterprise PeopleTools Fluid Core component (versions 8.58 and 8.59) allows unauthenticated attackers with network access via HTTP to achieve partial read and write access to accessible data. The attack requires human interaction (e.g., tricking a user into clicking a malicious link) and represents a scope change vulnerability where attacks may impact additional products beyond the primary target.
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.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 installed PeopleTools versionLog into PeopleSoft Application Designer or access the PeopleTools version via SQL query on PSSTATUS or via the About PeopleSoft page in the browser. Alternatively, check the PS_HOME directory for the tools version file or use the psadmin utility to view version information.Affected if The installed version is 8.58 or 8.59 exactly.
-
Confirm Fluid Core component is in useCheck if any Fluid-based pages or components are deployed and accessible in the PeopleSoft application. This can be verified by reviewing the PeopleSoft Application Designer for Fluid-enabled applications or checking the web profile configuration for Fluid settings.Affected if Fluid pages are enabled and accessible in the PeopleSoft environment.
-
Assess HTTP/HTTPS network exposureDetermine if the PeopleSoft web servers (PIA - PeopleSoft Internet Architecture) are reachable from untrusted networks. Check firewall rules, load balancer configurations, or web server bindings to identify external accessibility.Affected if PeopleSoft HTTP/HTTPS ports are accessible from untrusted or public networks.
-
Review web access logs for suspicious patternsExamine web server access logs (typically in the WEB_LOG directory or via the web profile) for anomalous HTTP requests, particularly those involving Fluid endpoints with unusual parameters or repeated requests that may indicate scanning or exploitation attempts.Affected if Unusual or malicious HTTP requests targeting Fluid endpoints are found in the logs.
You are affected if you have PeopleTools version 8.58 or 8.59 with Fluid Core enabled and exposed to untrusted network access via HTTP/HTTPS.
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 Oracle Critical Patch Updates for PeopleSoft Enterprise PeopleTools 8.58 and 8.59. If immediate patching is not possible, restrict HTTP/HTTPS access to PeopleSoft applications to trusted networks only and monitor for suspicious activity.
PeopleSoft Enterprise PeopleTools 8.60 or later (or apply July 2022 CPU)
- 1. Apply Oracle Critical Patch Update (CPU) July 2022 which contains the fix for CVE-2022-21520
- 2. Alternatively, upgrade to PeopleSoft Enterprise PeopleTools 8.60 or later which includes the security fix
- 3. After applying the patch or upgrade, verify the Fluid Core component is no longer vulnerable
- 4. Test the PeopleSoft applications to ensure functionality is maintained after the update
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-21520 — 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-21520 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