CVE-2024-21283
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 HCM Global Payroll Core product of Oracle PeopleSoft (component: Global Payroll for Core). Supported versions that are affected are 9.2.48-9.2.50. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise HCM Global Payroll Core. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all PeopleSoft Enterprise HCM Global Payroll Core accessible data as well as unauthorized access to critical data or complete access to all PeopleSoft Enterprise HCM Global Payroll Core accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 confidenceThis is an authorization bypass vulnerability in PeopleSoft Enterprise HCM Global Payroll Core affecting versions 9.2.48-9.2.50. A low-privileged attacker with network access via HTTP can exploit this to gain unauthorized creation, deletion, or modification access to critical payroll data, as well as unauthorized read access to sensitive data. The CVSS vector indicates high confidentiality and integrity impacts with no availability impact.
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.2.48, <= 9.2.50CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 PeopleSoft Enterprise versionQuery the PeopleSoft version information via the PeopleSoft PIA homepage, About page, or database version tables (such as PSVERSION or PSSTATUS). Compare the reported version to the affected range 9.2.48 through 9.2.50.Affected if The installed version is 9.2.48, 9.2.49, or 9.2.50.
-
Confirm Global Payroll Core module is deployedVerify that the Global Payroll Core (GP_CORE) application module is installed and active in the PeopleSoft environment. Check via PeopleSoft Application Designer, or query the PSMODULE table for active payroll-related modules.Affected if Global Payroll Core is installed and active in the environment.
-
Verify HTTP exposure of PeopleSoft servicesDetermine whether the PeopleSoft Internet Architecture (PIA) HTTP listeners are exposed to untrusted networks. Review web server configuration (Oracle WebLogic, IBM HTTP Server) and firewall rules to confirm whether HTTP/HTTPS ports are accessible from outside the trusted network.Affected if PeopleSoft HTTP services are reachable from untrusted network segments or the public internet.
-
Audit Global Payroll user role assignmentsReview user roles and permissions assigned in PeopleSoft Global Payroll. Use the Security Administrator component to list roles with payroll data access (such as GP_PAYROLL, GP_MANAGER, or custom payroll roles) and identify low-privileged users who should not have create, modify, or delete access to payroll data.Affected if Low-privileged users (such as those with basic employee or consultant roles) have been granted payroll data modification roles or permissions.
The environment is affected if it runs PeopleSoft Enterprise version 9.2.48, 9.2.49, or 9.2.50 with Global Payroll Core enabled and HTTP services are accessible to untrusted networks, allowing a low-privileged attacker to exploit the authorization bypass.
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 Critical Patch Update addressing this vulnerability when released. In the interim, restrict network access to the PeopleSoft HTTP services to trusted IPs only and review user role permissions in Global Payroll for Core.
- 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-2024-21283 — 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-2024-21283 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