CVE-2025-21561
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 SCM Purchasing product of Oracle PeopleSoft (component: Purchasing). 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 SCM Purchasing. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of PeopleSoft Enterprise SCM Purchasing accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise SCM Purchasing 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 · high confidenceInjection vulnerability in PeopleSoft Enterprise SCM Purchasing component (v9.2) allowing low-privileged network attackers unauthorized read, insert, update, and delete access to a subset of Purchasing data via HTTP.
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 PeopleSoft Enterprise SCM Purchasing installationLocate the PeopleSoft installation directory and check for the SCM Purchasing component. Common paths include PS_HOME or domain configurations. Look for application server or web server configurations referencing ' Purchasing' or 'eProcurement' modules.Affected if PeopleSoft Enterprise SCM Purchasing component is present on the system
-
Determine the exact version of PeopleSoft SCM PurchasingCheck the installed version by querying the PeopleSoft About page, psadmin utility, or version.txt in the PS_HOME directory. Look for version identifier showing 9.2.Affected if Version is exactly 9.2
-
Verify the Purchasing component is web-exposedCheck web server configuration (e.g., web.xml, psft.properties, or web server access logs) for HTTP endpoints serving the Purchasing module. Look for URLs containing /scm/purchasing/, /eProcurement/, or similar Purchasing-related paths.Affected if HTTP access to Purchasing component is enabled and exposed via web server
-
Confirm low-privileged user access is possibleReview PeopleSoft permission lists, roles, and user profiles to determine if low-privileged (non-admin) network users can access the Purchasing component. Check security configuration in PeopleSoft Security Administrator.Affected if Low-privileged users have network access to the Purchasing component via HTTP
-
Check network accessibility of Purchasing endpointsFrom a network perspective, verify HTTP/HTTPS ports serving the Purchasing application are accessible. Review firewall rules and web server bindings to confirm the component is reachable over the network.Affected if Purchasing component is reachable over the network without proper network segmentation
Environment is affected if PeopleSoft Enterprise SCM Purchasing version 9.2 is installed with the Purchasing component exposed via HTTP to the network, allowing low-privileged users to access it.
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 Oracle PeopleSoft Critical Patch Update addressing CVE-2025-21561; until patched, restrict network access to Purchasing modules and implement WAF rules for suspicious patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21561 — 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-2025-21561 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