CVE-2024-21264
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 CC Common Application Objects product of Oracle PeopleSoft (component: Activity Guide Composer). 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 CC Common Application Objects. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of PeopleSoft Enterprise CC Common Application Objects accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise CC Common Application Objects 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:N/S:U/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 confidenceThis is an injection-type vulnerability in the Activity Guide Composer component of PeopleSoft Enterprise CC Common Application Objects version 9.2. A low-privileged attacker with network access via HTTP can exploit this flaw to achieve unauthorized read access to a subset of data as well as unauthorized update, insert, or 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= 9.2CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 PeopleSoft Cost Center Common Application Objects versionAccess PeopleSoft EnterpriseOne or PeopleTools and locate the version information for the Cost Center Common Application Objects component. This is typically found in the system information, about page, or via SQL query on the PSVERSION table for the related product ID.Affected if The installed version is exactly 9.2 (version equals 9.2)
-
Confirm Activity Guide Composer component is presentNavigate to the PeopleSoft Navigator or use the Component Search functionality to locate the Activity Guide Composer component (commonly accessed via the Enterprise Components menu). Check if the component is registered in the system.Affected if The Activity Guide Composer component exists and is registered in the PeopleSoft environment
-
Verify HTTP/HTTPS network accessibilityDetermine if the PeopleSoft web servers (PIA - PeopleSoft Internet Architecture) are accessible via HTTP (port 80/443 or custom ports) from network locations outside the trusted internal network. Check firewall rules, load balancer configurations, and web server bindings.Affected if The PeopleSoft HTTP/HTTPS endpoints are reachable from untrusted or external network segments
-
Check for low-privileged user accounts with web accessReview the PeopleSoft security configuration to identify user profiles with low-privileged roles (such as PSUSER or similar) that have access to the web interfaces and the Activity Guide Composer component.Affected if Low-privileged user accounts with network web access exist and have permissions to access the Activity Guide Composer
-
Inspect Activity Guide data access permissionsExamine the security permissions (row-level security, permission lists, and role assignments) associated with the Activity Guide Composer to determine what data the component can read or modify.Affected if The component has access to sensitive data that could be read or modified through the vulnerability
You are affected if you are running exactly version 9.2 of PeopleSoft Enterprise Cost Center Common Application Objects with the Activity Guide Composer component enabled and accessible via HTTP from a network where low-privileged attackers can reach the application.
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 for PeopleSoft Enterprise 9.2 that addresses this vulnerability. Additionally, restrict network access to PeopleSoft systems to trusted sources and ensure the principle of least privilege is enforced for user accounts.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21264 — 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-21264 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