dbcve.org
Peoplesoft Enterprise PeopletoolsApplication · Oracle

CVE-2022-21369

MEDIUM · 6.1 CVSS v3.1 Published 2022-01-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Vulnerability in the PeopleSoft Enterprise PeopleTools product of Oracle PeopleSoft (component: Rich Text Editor). 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 confidence

This is a cross-site scripting (XSS) vulnerability in the Rich Text Editor component of Oracle PeopleSoft Enterprise PeopleTools versions 8.57, 8.58, and 8.59. An unauthenticated remote attacker can exploit this through HTTP requests, requiring human interaction (such as clicking a malicious link), allowing unauthorized read and limited write access to application data.

MitigationApply the relevant Oracle security patch for PeopleSoft Enterprise PeopleTools. If immediate patching is not feasible, consider disabling or restricting access to the Rich Text Editor component and implementing input validation/sanitization as a compensating control.

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
Peoplesoft Enterprise PeopletoolsApplication
Affected:= 8.57= 8.58= 8.59

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed PeopleTools version
    Access PeopleSoft Application Designer or use the following SQL query against the database: SELECT version FROM psoptions. Alternatively, check the About PeopleSoft page in the PIA (PeopleSoft Internet Architecture) or examine the PS_HOME directory for version files.
    Affected if The installed version matches 8.57, 8.58, or 8.59 exactly.
  2. Confirm the Rich Text Editor component is accessible
    Access the PeopleSoft Pure Internet Architecture portal and navigate to any page that utilizes the Rich Text Editor, such as the Message Catalog or Notification configurations. The component is typically accessed via the Rich Text Editor field type in Application Designer or through web-based forms.
    Affected if The Rich Text Editor interface loads and accepts user input without additional authentication beyond portal login.
  3. Check for unauthenticated access to Rich Text Editor endpoints
    Examine the PeopleSoft web configuration files (webservic.xml, webprofile configuration) and the PeopleSoft Interaction Hub settings. Verify whether the Rich Text Editor servlet endpoints (such as /psc/ps/EMPLOYEE/HRMS/c/PT_NEWS_FEED.RichTextEditor.*) are exposed to unauthenticated users.
    Affected if The Rich Text Editor servlet or its endpoints are accessible without requiring full PeopleSoft authentication.
  4. Review PeopleSoft web configuration for XSS filter settings
    Examine the PeopleSoft web profile configuration (webprofile.properties or via PIA administration) for the RSS_RENDER_XSS filter settings and input validation configurations. Check whether Oracle's Security Technical Implementation Guide (STIG) recommendations have been applied.
    Affected if XSS filtering is disabled or the web profile lacks proper input validation controls for the Rich Text Editor.

The environment is affected if the installed PeopleTools version is exactly 8.57, 8.58, or 8.59 AND the Rich Text Editor component is enabled and accessible to users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Oracle security patch for PeopleSoft Enterprise PeopleTools. If immediate patching is not feasible, consider disabling or restricting access to the Rich Text Editor component and implementing input validation/sanitization as a compensating control.

Fix this in Peoplesoft Enterprise Peopletools Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21369 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-21369 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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