dbcve.org
Peoplesoft Enterprise Human Capital Management EperformanceApplication · Oracle

CVE-2016-3460

MEDIUM · 5.4 CVSS v3.0 Published 2016-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Unspecified vulnerability in the PeopleSoft Enterprise HCM component in Oracle PeopleSoft Products 9.2 allows remote authenticated users to affect confidentiality and integrity via vectors related to ePerformance.

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

CVE-2016-3460 is an unspecified vulnerability in PeopleSoft Enterprise HCM version 9.2's ePerformance component. It allows remote authenticated users to impact confidentiality and integrity, indicating potential unauthorized data access or modification. The medium CVSS score suggests the attack requires some level of sophistication or specific conditions.

MitigationApply the Oracle Critical Patch Update that addresses this vulnerability (June 2016 CPU). Ensure ePerformance access is restricted to authenticated users with verified roles and monitor for unauthorized access patterns.

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 Human Capital Management EperformanceApplication
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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/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 checks

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

  1. Identify installed PeopleSoft Enterprise HCM version
    Access the PeopleSoft Enterprise HCM system via the web portal and navigate to the About page, or query the PeopleTools version table (PSSTATUS or similar) using SQL to determine the exact release version. Compare the version number to the affected range (9.2).
    Affected if The installed version is exactly 9.2
  2. Confirm ePerformance component is enabled
    Check the PeopleSoft Application Designer or web menu for the ePerformance module. In the PeopleSoft portal, navigate to Enterprise Components > Performance > ePerformance, or verify through the PeopleTools Security > Component Permissions to see if ePerformance components (such as GP_SS_SIGNIN, GP_SS_EE_SELF, or related) are registered and accessible.
    Affected if ePerformance components are present and accessible in the system
  3. Verify user role assignments for ePerformance
    Use PeopleSoft Security Administrator (PeopleTools > Security > User Profiles) or query the PSROLEUSER table to review which roles have access to ePerformance-related components. Check if roles like Employee Self-Service, Manager Self-Service, or Performance Manager are assigned to users.
    Affected if Roles granting ePerformance access are assigned to users, particularly to unaudited or external accounts
  4. Review ePerformance web catalog and menu access
    Navigate to PeopleTools > Portal > Structure and Content to examine the ePerformance folder structure and content references. Check which web libraries (such as GP_SS_RMT) and service operations are exposed in the ePerformance menu.
    Affected if ePerformance menus and web libraries are publicly accessible or not restricted to verified internal users
  5. Inspect authentication and single sign-on configuration
    Examine the PeopleTools > Security > Signon Settings and any SSO configuration (such as LDAP or Kerberos integration). Verify that authentication is required for all ePerformance URLs and that session tokens are properly validated.
    Affected if ePerformance can be accessed without strong authentication or session validation is disabled

You are affected if your PeopleSoft Enterprise HCM is version 9.2 and the ePerformance component is enabled and accessible to authenticated users, as the vulnerability allows impact to confidentiality and integrity through the unspecified flaw in this component.

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 Oracle Critical Patch Update that addresses this vulnerability (June 2016 CPU). Ensure ePerformance access is restricted to authenticated users with verified roles and monitor for unauthorized access patterns.

Fix this in Peoplesoft Enterprise Human Capital Management Eperformance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Check whether your project pulls in CVE-2016-3460 — 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-2016-3460 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