CVE-2026-35241
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 CS Student Records product of Oracle PeopleSoft (component: Research Tracking). 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 CS Student Records. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all PeopleSoft Enterprise CS Student Records accessible data. CVSS 3.1 Base Score 5.7 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/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 access control vulnerability in the Research Tracking component of PeopleSoft Enterprise CS Student Records 9.2. The flaw allows low-privileged attackers with network access to access sensitive data through the application, but requires human interaction (likely a legitimate user to initiate or validate the request). The high confidentiality impact (C:H) with no integrity or availability impact suggests it's primarily an Insecure Direct Object Reference (IDOR) or broken access control issue allowing unauthorized data disclosure.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/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.
-
Confirm PeopleSoft Student Records versionQuery the PeopleSoft version information through the About page (Navigation: About > About PeopleSoft Enterprise) or check the PSVERSION table in the database for the application release version. Verify it is exactly 9.2.Affected if The installed version is exactly 9.2 (version equality match)
-
Identify if Research Tracking component is deployedCheck the PeopleSoft Application Designer or navigate to the Research Tracking component (typically under Student Records > Research Tracking menu). Verify whether the component exists and is accessible in the current environment.Affected if The Research Tracking component is present and accessible in the environment
-
Check Research Tracking component security settingsNavigate to PeopleTools > Security > Permissions & Roles > Permission Lists or Role permissions. Locate permissions granted to the Research Tracking component (CS_RSRCH_TRACKING or similar). Identify which roles and permission lists have access.Affected if Low-privileged roles (such as Visitor, Contributor, or non-admin roles) have access to the Research Tracking component
-
Verify access control on research data recordsUse the Research Tracking component to attempt accessing different student research records. Check whether users with minimal privileges can view research data they should not have access to, indicating broken object-level authorization.Affected if Users with low-privileged roles can access sensitive research data they are not authorized to view
-
Audit component interface for direct object referencesInspect URLs and form parameters when using the Research Tracking component. Look for predictable or enumerable parameter values (such as IDs) that could allow unauthorized access to other records without proper authorization checks.Affected if The component exposes direct object references (such as record IDs) in URLs or forms that can be manipulated to access unauthorized data
You are affected if your environment runs PeopleSoft Enterprise CS Student Records version 9.2 and the Research Tracking component is accessible to low-privileged users who can view data beyond their authorized scope.
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 PeopleSoft patch for version 9.2, or implement compensating controls such as strict role-based access control (RBAC) policies and additional authorization checks on the Research Tracking component.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35241 — 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-2026-35241 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