Peoplesoft EnterpriseApplication · Oracle

CVE-2024-21286

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 ELM Enterprise Learning Management product of Oracle PeopleSoft (component: Enterprise Learning Management). The supported version that is affected is 9.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise ELM Enterprise Learning Management. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in PeopleSoft Enterprise ELM Enterprise Learning Management, 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 ELM Enterprise Learning Management accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise ELM Enterprise Learning Management accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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 confidence

A vulnerability in PeopleSoft Enterprise ELM version 9.2 allows a low-privileged attacker with network access via HTTP to achieve unauthorized read and write (insert/update/delete) access to a subset of the application's data. The attack requires human interaction and may impact additional products due to scope change.

MitigationApply the relevant Oracle patch for PeopleSoft Enterprise ELM 9.2. If no patch is immediately available, restrict network access to the ELM HTTP endpoints and review user permissions for the Enterprise Learning Management component.

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 EnterpriseApplication
Affected:= 9.2

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm PeopleSoft Enterprise ELM is installed
    Check your application inventory or look for PeopleSoft components related to Enterprise Learning Management (ELM) in your environment
    Affected if The system runs PeopleSoft Enterprise ELM version 9.2
  2. Verify the exact ELM version number
    Access the PeopleSoft About page or check the installed software version through the PeopleSoft Installation Navigator, or query the PSVERSION table for the ELM product version
    Affected if The installed version is exactly 9.2 (the affected version is version = 9.2, meaning only this specific version)
  3. Determine if HTTP endpoints are network-accessible
    Check network exposure of ELM web interfaces. Verify if the PeopleSoft HTTP/ICS listeners are exposed to untrusted networks or the public internet rather than being restricted to internal networks
    Affected if ELM HTTP endpoints are accessible from untrusted network locations (the CVE requires network access via HTTP)
  4. Review Enterprise Learning Management component permissions
    Check user role assignments and permission lists granted to low-privileged users for the Enterprise Learning Management component in PeopleSoft Security configuration
    Affected if Low-privileged users have been granted any permissions to the ELM component (the attack allows unauthorized access to ELM data)

Your environment is affected only if you are running PeopleSoft Enterprise ELM version exactly 9.2 AND have HTTP endpoints network-accessible AND low-privileged users have any ELM permissions.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Oracle patch for PeopleSoft Enterprise ELM 9.2. If no patch is immediately available, restrict network access to the ELM HTTP endpoints and review user permissions for the Enterprise Learning Management component.

Recommended fix Moderate confidence

Apply latest Oracle Critical Patch Update (CPU) - check January 2025 CPU or later for this specific CVE fix

  1. 1. Subscribe to Oracle Critical Patch Updates to receive security notifications at https://www.oracle.com/security-alerts/
  2. 2. Apply the latest Oracle Critical Patch Update (CPU) for PeopleSoft products. For CVE-2024-21286, this was addressed in the January 2025 CPU or later.
  3. 3. After applying the CPU patch, verify the fix by checking the Oracle PeopleSoft Enterprise ELM component version or by reviewing the CPU advisory for confirmation that CVE-2024-21286 is addressed.
  4. 4. Test the Enterprise Learning Management module in a non-production environment to ensure normal functionality after patching.
  5. 5. Deploy the patched update to production following your organization's change management process.
Caveat Oracle CPU patches are cumulative and generally safe; however, test thoroughly in non-production as patches may affect ELM module behavior

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Peoplesoft Enterprise Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21286 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21286 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