Peoplesoft EnterpriseApplication · Oracle

CVE-2007-3869

HIGH · 7.5 CVSS v2.0 Published 2007-07-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Multiple unspecified vulnerabilities in the Customer Relationship Management Online Marketing component in Oracle PeopleSoft Enterprise 8.9 Bundle 26 and 9.0 Bundle 7 allow remote authenticated users to have an unknown impact, aka (1) PSE04 and (2) PSE05.

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

This CVE addresses multiple unspecified vulnerabilities in the Oracle PeopleSoft Enterprise CRM Online Marketing component, affecting versions 8.9 Bundle 26 and 9.0 Bundle 7. The vulnerabilities allow remote authenticated users to execute actions with unknown impact, assigned CVSS 7.5 (HIGH). The issues are categorized as PSE04 and PSE05 in Oracle's advisory matrix.

MitigationApply Oracle Critical Patch Updates from 2007 for PeopleSoft Enterprise 8.9 and 9.0, specifically the patches addressing CRM Online Marketing component vulnerabilities. If patches are unavailable for these legacy versions, consider upgrading to a supported PeopleSoft release.

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 EnterpriseApplication
Affected:= 8.9= 9.0

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 PeopleSoft Enterprise version
    Query the PeopleSoft database or check the PSVERSION table: SELECT version FROM psversion WHERE objid = ' Peoplesoft'; Or use the PeopleSoft Application Designer to view system information.
    Affected if Installed version is exactly 8.9 or 9.0 (or falls within these release lines with bundles 26 or 7 respectively)
  2. Verify Online Marketing component is deployed
    Check the PeopleSoft component registry in the PSPCMPROG table or examine the Online Marketing application menus and pages under the CRM module. Look for components under the 'Online Marketing' or 'Marketing' navigation structure.
    Affected if Online Marketing component exists and is accessible in the PeopleSoft menu structure
  3. Confirm CRM module is enabled
    Check PeopleSoft Permission Lists and Security tables (PSPERMISSIONS, PSROLECLASS) to verify the CRM component is active. Review the PeopleSoft Portal configuration for CRM Online Marketing navigation.
    Affected if CRM module with Online Marketing functionality is registered and accessible
  4. Check for remote authentication access
    Review PeopleSoft web profile configuration (PSWEBPROFDEFNL) and Internet Architecture settings to determine if remote (non-PeopleSoft) authentication is permitted. Inspect PSACCESSPRFL table for external access profiles.
    Affected if Remote authenticated users can access the PeopleSoft web interface and CRM Online Marketing

A system is affected if it runs PeopleSoft Enterprise 8.9 or 9.0 with the CRM Online Marketing component deployed and accessible to remote authenticated users.

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 Oracle Critical Patch Updates from 2007 for PeopleSoft Enterprise 8.9 and 9.0, specifically the patches addressing CRM Online Marketing component vulnerabilities. If patches are unavailable for these legacy versions, consider upgrading to a supported PeopleSoft release.

Fix this in Peoplesoft Enterprise Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-3869 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-3869 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