CVE-2016-0680
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 · uneditedUnspecified vulnerability in the PeopleSoft Enterprise SCM component in Oracle PeopleSoft Products 9.1 and 9.2 allows remote authenticated users to affect confidentiality and integrity via vectors related to Services Procurement.
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 · low confidenceCVE-2016-0680 is an unspecified vulnerability in PeopleSoft Enterprise SCM (Supply Chain Management) versions 9.1 and 9.2, specifically affecting the Services Procurement module. The vulnerability allows remote authenticated users to impact confidentiality and integrity, likely through improper access controls or input validation within the Services Procurement functionality.
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.1= 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.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 checksWork through these to decide whether this CVE applies to you.
-
Identify PeopleSoft SCM versionAccess PeopleSoft Application Designer or the PeopleSoft Enterprise Portal and navigate to About > Version Information to determine the installed version of PeopleSoft Enterprise SCM (Supply Chain Management)Affected if The installed version is 9.1 or 9.2
-
Confirm Services Procurement module is activeLog into the PeopleSoft Enterprise Portal and check whether the Services Procurement component (typically found under Procurement > Services Procurement) is accessible or enabled in the systemAffected if The Services Procurement module is present and accessible to authenticated users
-
Review access control configuration for Services ProcurementAccess the PeopleSoft Security configuration under PeopleTools > Security > Permissions & Roles and examine the permission lists assigned to user roles that have access to the Services Procurement functionalityAffected if Users have broader access permissions to Services Procurement than their assigned roles should permit
-
Audit Services Procurement transaction logsReview PeopleSoft process monitoring and transaction logs (using Process Monitor and the Services Procurement audit tables) for any unexpected data access or modification activitiesAffected if There are unauthorized access attempts or unexpected data exposures within Services Procurement transactions
You are affected if you run PeopleSoft Enterprise SCM versions 9.1 or 9.2 with the Services Procurement module enabled and accessible to authenticated users.
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 relevant Oracle Critical Patch Update (CPU) for April 2016 that addresses CVE-2016-0680. Until patched, limit access to the Services Procurement module to only trusted authenticated users and monitor for anomalous access patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0680 — 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-2016-0680 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